zcorpan

5 ms·

1.
by zcorpan 1y ago
Good point! We've adjusted the plan so that it's 100% of beta (starting today). Thanks.
2.
by zcorpan 1y ago
The spec allows multiple top-level headings: https://html.spec.whatwg.org/multipage/sections.html#heading...
3.
by zcorpan 1y ago
TFA has been fixed to make this clearer. Thanks!
4.
by zcorpan 1y ago
As of 2022 (when the outline algorithm was removed from the spec), it's a problem with your website implementation.
5.
by zcorpan 1y ago
They do if you include <meta name="color-scheme" content="light dark"> Also see https://github.com/whatwg/html/issues/5426
6.
by zcorpan 1y ago
There is no warning in that case.
7.
by zcorpan 1y ago
Nested lists have 0 block-margin and different list-style-type. But that seems to be about it...
8.
by zcorpan 1y ago
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.
9.
by zcorpan 1y ago
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.
10.
by zcorpan 1y ago
What is your bug?
11.
by zcorpan 1y ago
Someone has to be first. :-)
12.
by zcorpan 1y ago
There's a new proposal to address this: https://github.com/whatwg/html/issues/5033
13.
by zcorpan 1y ago
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.
14.
by zcorpan 1y ago
Fixed, thanks.
15.
by zcorpan 1y ago
Good point. Now fixed!
16.
by zcorpan 1y ago
Yes.
17.
by zcorpan 1y ago
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
18.
by zcorpan 1y ago
It has been in the spec since 2009: https://github.com/whatwg/html/commit/0ed655652d52f0ab068fcb...
19.
by zcorpan 1y ago
Chrome doesn't implement the change yet, only the deprecation warning. So you can check the console in devtools or run a Lighthouse check.
20.
by zcorpan 1y ago
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), twice: https:/&#
21.
by zcorpan 1y ago
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 h
22.
by zcorpan 1y ago
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 fo
23.
by zcorpan 2y ago
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
24.
by zcorpan 6y ago
Blog post about the guide: https://bocoup.com/blog/introducing-the-web-platform-contrib...
25.
by zcorpan 10y ago
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; whit