zcorpan
zcorpan on Hacker News
Good point! We've adjusted the plan so that it's 100% of beta (starting today). Thanks.
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.
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.
Someone has to be first. :-)
This is already the case, the warning is only for h1 in article/aside/nav/section. I'll fix the article to make this clearer, thanks.
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 on some pages is expected and is acceptable. Sites becoming unusable is not acceptable.
Chrome doesn't implement the change yet, only the deprecation warning. So you can check the console in devtools or run a Lighthouse check.
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 website if they have a bug, or apply a sitepatch. We're also monitoring the broken website reports for regressions from this change in particular.
I understand that a rollout makes reproduction harder, and not everyone will be aware of the change. It's a tradeoff when deciding whether to do a rollout or ride the trains normally.
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 employ. It allows for course-correcting if necessary and is less disruptive than shipping to 100% of users directly.
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 says, that is likely to translate identically when writing a second implementation.