eric, 2 months ago

@brucelawson They bypassed the standards process and yeeted something out that has issues with a label assigned to it. Clown shit.

hdv, 2 months ago

@eric @brucelawson could you expand on ‘bypassed’?

eric, 2 months ago

@hdv Well, no other browser supports it, and it showed up relatively out of the blue. @brucelawson

eeeps, 2 months ago

@eric @hdv @brucelawson Spec discussion was here & in OpenUI.

https://github.com/whatwg/html/pull/9546

I think they got "we like this but there are details to be worked out" from both Mozilla and Chromium.

• https://github.com/whatwg/html/pull/9546#issuecomment-1741530259
• https://github.com/whatwg/html/pull/9546#issuecomment-1775313390

No TAG design review.

I give ’em a C- for process. At least there was a spec proposal followed by time, discussions, refinements, and platform tests. But sounds like no one else thought it was READY-ready; spec PR wasn't merged.

eeeps, 2 months ago

@eric @hdv @brucelawson Maybe I need to raise my expectations. Like, sounds like a lil' Accessible Platform Architectures Working Group horizontal review would have gone a long way.

eric, 2 months ago

@eeeps Yup, and instead they took a wet shit across the entire internet that will have a decades-long tail of interop problems to clean up. @hdv @brucelawson

aardrian, 2 months ago

@eric @eeeps @hdv
Let’s not forget Apple’s own demo was broken because they were so quick to rush out a “FIRST” post:
https://bugs.webkit.org/show_bug.cgi?id=270377

Almost the same playbook as <hr> in <select>:
https://adrianroselli.com/2023/10/splitting-within-selects.html#History-HR

@brucelawson

patrick_h_lauke, 2 months ago

@aardrian @eric @eeeps @hdv @brucelawson i LOL'd "While browsers can always make conscious decisions to ship unilaterally, we should always try to reach consensus first" https://github.com/whatwg/html/pull/9546#issuecomment-1989739381

aardrian, 2 months ago

@patrick_h_lauke
Genuine lulz there.

@eric @eeeps @hdv @brucelawson