w3ctag/design-principles
View on GitHub ↗ ★ 227 Bikeshed
A set of design principles to be used when designing web platform technologies
7 mentions on Hacker News by 7 people: 2 stories, 5 comments · first 2018-02-09 · latest 2024-11-11
20082026
-
…apparently been significantly watered down from what it was originally—see the initial proposal in https://github.com/w3ctag/design-principles/pull/75 , and what was then merged in https://github.com/w3ctag/design-principles/pull/89 .
comment by chrismorgan · 2024-11-11 · in Web Locks API -
…that page, dcodeIO (from the AssemblyScript community) was definitely not behaving in good faith: https://github.com/w3ctag/design-principles/issues/322 It seems most of the complaints are that selecting UTF-8 as a primary string encoding…
comment by Jasper_ · 2022-09-08 · in The Risks of WebAssembly -
▲ 6
Do not design around third-party tools unless it breaks the Webstory by robin_reala · 2021-10-20 · 0 comments
-
▲ 1
New principle: Do not design around 3rd party tools unless it breaks the Webstory by anandchowdhary · 2021-09-20 · 0 comments
-
…man ever created for everything that uses or opted to preserve the semantics of 16-bit Unicode". https://github.com/w3ctag/design-principles/issues/322#issue... I'd argue that the fundamental bug here is in splitting a string in between…
comment by conrad-watt · 2021-07-27 · in An Urgent Notice from AssemblyScript -
…are in any case not required to). https://w3c.github.io/webappsec-secure-contexts/#localhost" [1] https://github.com/w3ctag/design-principles/pull/75#issuecom...
comment by aurelian15 · 2018-02-09 · in Chrome 68 will mark all HTTP sites as “not secure” -
…I think it's probably worth jumping into that discussion before the policy is set in stone. [1] https://github.com/w3ctag/design-principles/pull/75
comment by andrewla · 2018-02-09 · in Chrome 68 will mark all HTTP sites as “not secure”