3 ms·
No they wouldn't. I can't think of a single thing in any browser that was implemented after a standard was created. It's always been driven by one browser jus
by jedberg 3y ago
No they wouldn't. I can't think of a single thing in any browser that was implemented after a standard was created. It's always been driven by one browser just doing a thing, then other browsers do it slightly differently, then the standards body comes together and they settle on the-one-true-way and everyone updates their support to match the standard.
- mnw21cam 3y ago[flagged]
- jedberg 3y agoLol ok let me say "most everyone mostly matches the standard" :)
- reaperducer 3y agoOh, the boundless optimism. How cute. Oh, pointless condescension on the internet. How cute.
- mvonballmo 3y agoIt very much used to work like this, pretty much exclusively. More recently, though (especially, the last couple of years), browser vendors work very closely with standards groups, contributing there, and looking for feedback from other browser vendors. At least in the CSS and JS space, the extensions to those standards have proceeded largely as a group effort rather than as you described.
- dwaite 3y agoThere's pretty much always implementations, but it is a huge headache when people rely on behavior which is not yet stable. The browsers have started to first ship things behind feature flags, and in Chrome's case also behind "Origin trials". We just have less need now for one browser to go off and define their own way for borders to be drawn as rounded rectangles. I suspect we'll see some funky CSS extensions ship pre-standardization for VR headsets, though. Things like controlling the z-axis height of <dialog> and other elements.