Seeing some excitement around this <h> proposal, but it's totally missing "why". https://github.com/w3c/html/issues/774 …
-
-
Replying to @jaffathecake
if h could be an option *along with* h2 etc. it could be a win for structuring data without taking away contextual overrides
1 reply 0 retweets 2 likes -
Replying to @Una @jaffathecake
its an outline model--outlines provide order & best practice architecture. Web isn't structured rn though so you'd need both
1 reply 0 retweets 0 likes -
Replying to @Una
there's already an outline model, just not implemented. The <h> proposal needs to demonstrate why it's better than the current outline.
2 replies 0 retweets 2 likes -
Replying to @jaffathecake
: if there's an outline model but nobody has it, does it really exist? ;-) /cc
@Una2 replies 0 retweets 4 likes -
Replying to @slightlylate @Una
right, but the assumption is that this new tag will somehow get the thing that doesn't exist.
2 replies 0 retweets 2 likes -
but the work to add the outline, and fix <h1>, is a subset of creating <h>. So then you don't need <h>.
3 replies 0 retweets 0 likes -
I suggested years ago we move <title> inside body (meta name="title" in head) to release h1
1 reply 0 retweets 1 like -
-
: I enjoy that you "well, actually...."'d my joke.
-
-
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.