News for hackers. Stuff that matters.

zcorpan

Re:Default styles for h1 elements are changing on Monday April 14, 2025 @12:02PM (#43682785)
Good point! We've adjusted the plan so that it's 100% of beta (starting today). Thanks.
Re:Default styles for h1 elements are changing on Sunday April 13, 2025 @03:45PM (#43675325)
The spec allows multiple top-level headings: https://html.spec.whatwg.org/multipage/sections.html#heading...
Re:Default styles for h1 elements are changing on Sunday April 13, 2025 @03:32PM (#43675242)
TFA has been fixed to make this clearer. Thanks!
Re:Default styles for h1 elements are changing on Friday April 11, 2025 @11:10AM (#43654698)
As of 2022 (when the outline algorithm was removed from the spec), it's a problem with your website implementation.
Re:Default styles for h1 elements are changing on Friday April 11, 2025 @11:08AM (#43654666)
They do if you include <meta name="color-scheme" content="light dark">

Also see https://github.com/whatwg/html/issues/5426

Re:Default styles for h1 elements are changing on Friday April 11, 2025 @11:03AM (#43654595)
There is no warning in that case.
Re:Default styles for h1 elements are changing on Friday April 11, 2025 @10:58AM (#43654528)
Nested lists have 0 block-margin and different list-style-type. But that seems to be about it...
Re:Default styles for h1 elements are changing on Friday April 11, 2025 @06:25AM (#43652343)
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.

Re:Default styles for h1 elements are changing on Friday April 11, 2025 @06:18AM (#43652312)
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.
Re:Default styles for h1 elements are changing on Friday April 11, 2025 @06:13AM (#43652288)
What is your bug?
Re:Default styles for h1 elements are changing on Friday April 11, 2025 @06:11AM (#43652274)
Someone has to be first. :-)
Re:Default styles for h1 elements are changing on Friday April 11, 2025 @06:06AM (#43652257)
There's a new proposal to address this: https://github.com/whatwg/html/issues/5033
Re:Default styles for h1 elements are changing on Friday April 11, 2025 @06:04AM (#43652246)
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.
Re:Default styles for h1 elements are changing on Friday April 11, 2025 @05:53AM (#43652180)
Fixed, thanks.
Re:Default styles for h1 elements are changing on Friday April 11, 2025 @05:51AM (#43652168)
Good point. Now fixed!
Re:Default styles for h1 elements are changing on Friday April 11, 2025 @05:46AM (#43652137)
Yes.
Re:Default styles for h1 elements are changing on Friday April 11, 2025 @05:44AM (#43652128)
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.
Re:Default styles for h1 elements are changing on Friday April 11, 2025 @03:38AM (#43651379)
Re:Default styles for h1 elements are changing on Friday April 11, 2025 @03:08AM (#43651248)
Chrome doesn't implement the change yet, only the deprecation warning. So you can check the console in devtools or run a Lighthouse check.
Re:Default styles for h1 elements are changing on Friday April 11, 2025 @03:05AM (#43651233)
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://github.com/whatwg/html/issues/7867#issuecomment-1977... https://github.com/whatwg/html/issues/7867#issuecomment-2595...

The next step is either rollout or ship directly.

Re:Default styles for h1 elements are changing on Friday April 11, 2025 @02:55AM (#43651185)
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.

Re:Default styles for h1 elements are changing on Friday April 11, 2025 @02:42AM (#43651117)
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.

Re:Firefox will consider a Rust implementation of JPEG-XL on Thursday September 05, 2024 @03:32AM (#41454405)
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.
Re:Web Platform Contribution Guide on Tuesday June 09, 2020 @06:13AM (#23465280)
Re:Google HTML/CSS Style Guide – Omit Optional Tags on Tuesday September 20, 2016 @08:27AM (#12538937)
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 allowed in noscript in head.