Issues: w3ctag/design-principles
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
New principle: Text-based syntaxes should be designed to be usable by humans
Agenda+
Topic: Meta
#453
opened Sep 11, 2023 by
LeaVerou
New principle: The value of HTML boolean attributes doesn't matter
Topic: HTML
#451
opened Aug 16, 2023 by
LeaVerou
New principle: Consider many & diverse use cases to avoid overfitting
Topic: Meta
#450
opened Aug 3, 2023 by
LeaVerou
New principle: Document whether to add things to Document, Navigator, Window, or SomeOtherInterface
#448
opened Jun 29, 2023 by
jyasskin
Should conceptually ordered enums still be strings?
tc39-tracker
Issues where TC39 input would be useful
Topic: JS
#443
opened May 16, 2023 by
LeaVerou
"Make method arguments optional if possible" section has bad advice
#437
opened Apr 22, 2023 by
bakkot
Make our principles more inclusive of non-Web JS APIs
tc39-tracker
Issues where TC39 input would be useful
Topic: JS
Topic: Meta
Topic: Web IDL
Has to do with Web IDL
#436
opened Apr 21, 2023 by
LeaVerou
Examples for "overloading" principle
editorial
Write Me
Text needs to be written.
#431
opened Apr 20, 2023 by
torgo
Clarify which enum the principle 6.11 is talking about
Topic: JS
Topic: Web IDL
Has to do with Web IDL
#427
opened Mar 22, 2023 by
saschanaz
New principle: Avoid adding (non-constructor) functions to the global scope
Agenda+
tc39-tracker
Issues where TC39 input would be useful
Topic: JS
Advice on JS passing points-in-time or offsets-from-now
tc39-tracker
Issues where TC39 input would be useful
Topic: JS
#425
opened Mar 14, 2023 by
jyasskin
Editorial: remove "when appropriate" from meaningful consent
editorial
#397
opened Sep 5, 2022 by
rhiaro
"Fully active" section should mention which error to throw if non-fully active docs are not supported
#395
opened Sep 2, 2022 by
johannhof
Previous Next
ProTip!
Mix and match filters to narrow down what you’re looking for.