Good point! We've adjusted the plan so that it's 100% of beta (starting today). Thanks.
The spec allows multiple top-level headings: https://html.spec.whatwg.org/multipage/sections.html#heading...
TFA has been fixed to make this clearer. Thanks!
As of 2022 (when the outline algorithm was removed from the spec), it's a problem with your website implementation.
They do if you include <meta name="color-scheme" content="light dark"> Also see https://github.com/whatwg/html/issues/5426
There is no warning in that case.
Nested lists have 0 block-margin and different list-style-type. But that seems to be about it...
The article says > Do not rely on default browser styles for conveying a heading hierarchy. Explicitly define your document hierarchy using <h2> for second-level headings, <h3> for third-level, etc.
It only worked visually. For screen reader users, all headings are level 1. If you switch to using h2 etc, it will be more accessible.
What is your bug?
There's a new proposal to address this: https://github.com/whatwg/html/issues/5033
Fixed, thanks.
Yes.
The feedback loop is Firefox's "report broken site" in the Help menu. Success is there are no reports about broken sites due to this change, or the breakage is minor -- differently sized headings and different margins…
It has been in the spec since 2009: https://github.com/whatwg/html/commit/0ed655652d52f0ab068fcb...
Chrome doesn't implement the change yet, only the deprecation warning. So you can check the console in devtools or run a Lighthouse check.
Some testing has already happened before starting the rollout. The change has been shipping in Firefox Nightly for a year. I have analyzed impact of affected pages in the HTTP Archive dataset (about 12,000,000 pages),…
Firefox also has a built-in "broken website" reporter in the Help menu, which sends a report to Mozilla. The WebCompat team analyzes those reports and can decide to report a Gecko bug if it has a bug, contact the…
To test in Firefox with the new behavior, set layout.css.h1-in-section-ua-styles.enabled to false in about:config. Rolling out potentially risky changes in this way is not new, and is also a strategy that other browsers…
I don't disagree that it's sufficient, but also, ideally different people would implement the spec. If you have a particular mental model or understanding of a part of the spec that doesn't match what the spec actually…
Blog post about the guide: https://bocoup.com/blog/introducing-the-web-platform-contrib...
http://software.hixie.ch/utilities/js/live-dom-viewer/saved/... In Chrome Canary 55.0.2866.0 the noscript element contains a text node and a link element. This matches the spec as far as I can tell; whitespace is…
Good point! We've adjusted the plan so that it's 100% of beta (starting today). Thanks.
The spec allows multiple top-level headings: https://html.spec.whatwg.org/multipage/sections.html#heading...
TFA has been fixed to make this clearer. Thanks!
As of 2022 (when the outline algorithm was removed from the spec), it's a problem with your website implementation.
They do if you include <meta name="color-scheme" content="light dark"> Also see https://github.com/whatwg/html/issues/5426
There is no warning in that case.
Nested lists have 0 block-margin and different list-style-type. But that seems to be about it...
The article says > Do not rely on default browser styles for conveying a heading hierarchy. Explicitly define your document hierarchy using <h2> for second-level headings, <h3> for third-level, etc.
It only worked visually. For screen reader users, all headings are level 1. If you switch to using h2 etc, it will be more accessible.
What is your bug?
There's a new proposal to address this: https://github.com/whatwg/html/issues/5033
Fixed, thanks.
Yes.
The feedback loop is Firefox's "report broken site" in the Help menu. Success is there are no reports about broken sites due to this change, or the breakage is minor -- differently sized headings and different margins…
It has been in the spec since 2009: https://github.com/whatwg/html/commit/0ed655652d52f0ab068fcb...
Chrome doesn't implement the change yet, only the deprecation warning. So you can check the console in devtools or run a Lighthouse check.
Some testing has already happened before starting the rollout. The change has been shipping in Firefox Nightly for a year. I have analyzed impact of affected pages in the HTTP Archive dataset (about 12,000,000 pages),…
Firefox also has a built-in "broken website" reporter in the Help menu, which sends a report to Mozilla. The WebCompat team analyzes those reports and can decide to report a Gecko bug if it has a bug, contact the…
To test in Firefox with the new behavior, set layout.css.h1-in-section-ua-styles.enabled to false in about:config. Rolling out potentially risky changes in this way is not new, and is also a strategy that other browsers…
I don't disagree that it's sufficient, but also, ideally different people would implement the spec. If you have a particular mental model or understanding of a part of the spec that doesn't match what the spec actually…
Blog post about the guide: https://bocoup.com/blog/introducing-the-web-platform-contrib...
http://software.hixie.ch/utilities/js/live-dom-viewer/saved/... In Chrome Canary 55.0.2866.0 the noscript element contains a text node and a link element. This matches the spec as far as I can tell; whitespace is…