I'm sure a lot of web folk are going to say "wow you're late to the party" but the fact that the <h1> tag's text size shrinks for every <article> or <section> it's inside of, but the other tags (like <h2>) do not.

That is a *BONKERS* decision and it's apparently intentional

@JoshJers i think the plan was to have them all shrink like that, but nobody did it so they just half- gave up?

@irina from the look of the standard it looks like it only calls out H1, I wonder if that was supposed to be an example and people took it literally?

https://html.spec.whatwg.org/multipage/rendering.html#sections-and-headings

it would definitely make *more* sense if they were to all shrink (or none shrink) though 😀

HTML Standard

@JoshJers i can't find the name of it so i can't find it, but i think the plan was they'd all do that, so they implemented it for h1, but nobody cared so they never did any more? something about using the article and section tags instead of the different H levels

someone will know the name of the thing I'm thinking of, but googling keywords has led me to nothing

@irina @JoshJers

Yeah pretty much

standards folks thought there needed to be an outline algorithm to determine the tree structure of headings that are out of order, and browser developers, accessibility experts, and screen reader devs all said they don't plan on implementing it https://www.w3.org/Bugs/Public/show_bug.cgi?id=25003

But the spec also included sample CSS that does this resizing and that part did make it into browsers somehow https://github.com/whatwg/html/issues/7867

25003 – modify required heading mappings to reflect reality

@irina @JoshJers funnily enough Firefox is slowly shipping a fix that removes that CSS because they wanna be careful about web compat https://bugzilla.mozilla.org/show_bug.cgi?id=1883896
1883896 - Remove UA styles for :is(article, aside, nav, section) h1 (Nightly only)

RESOLVED (zcorpan) in Core - Layout. Last updated 2024-12-16.

@Osmose @irina legitimately baffling they didn't just add like an <h> tag which is the variable one and leave <h1> alone while they were adding 8 million other tags

@JoshJers @Osmose @irina

"But we have to be backward compatible to people who only every used h1 and don't know about h."

Yeah, let's support very, very old websites that start with <!DOCTYPE html> ...

@wakame @JoshJers @Osmose @irina

I still run a couple of websites like that, so I'd rather they did stay supported.

@celesteh @JoshJers @Osmose @irina

Yes, by now we likely have websites that use both HTML 5 and can be described as "very, very old".

But back when HTML 5 was new, a decision to streamline headings a bit (just a little bit) would have been great.

@wakame @celesteh @Osmose @irina imo they should have added a new <h> tag and had that be the "use this and it'll change size as you dip into sections" or something, and left h1-6 alone
Embroidery Trouble Shooting Page

Embroidery Trouble Shooting Answers to all your questions about Embroidery problems

@Yuvalne @JoshJers @Osmose @irina

Reminds me of this "boost" behavior in Android Chrome:
"If you don't explicitly set the font size, we assume that it's a 'legacy' website and simply set a huge fontsize for you."

@Yuvalne @wakame @Osmose @irina god this site makes me fucking lose it every time I see it again