#246: HTML General Review: HTML Styling
Discussions
Comment by @torgo Jul 24, 2018 (See Github)
Discussed the issue of lack of async
and defer
on the <style>
element. Some further research required before raising this as an issue.
Comment by @dbaron Jul 24, 2018 (See Github)
I think it would really be controls for <link rel=stylesheet>
... which is annoying because link
is so general.
Comment by @hober Dec 10, 2019 (See Github)
Given our new process for annual HTML reviews, I think we should forward-dupe this to #456 and close.
OpenedApr 17, 2018
Hello TAG!
This issue is part of the TAG's larger effort to review the HTML spec in its entirety--please see the original issue https://github.com/w3ctag/design-reviews/issues/174 for a summary of all the break-out issues.
The "Sections" are all the sections of the WHATWG HTML spec that should be reviewed as part of this issue. Where the spec section has associated Web Platform Tests, the specific WPT path is noted. While the primary focus of the review is the specification text, it can be helpful to review the related tests to help clarify algorithms or see interoperability conformance issues (or find issues with the tests).
The "Features" are just a sample of what you will encounter as part of this spec section, it's not meant to be exhaustive.
Here are some example suggestions for what to look for during the review, but don't limit to only these suggestions!
innerText
(returns an element's text "as rendered")<style>
Please provide feedback as (please select one):