I don't know enough honestly. That's my fear from the outside and without deep knowledge
-
-
Turns out, Browser engineers usually aren't competent to answer either of those questions! So we require teams to seek external feedback and review, both from the
@w3ctag and from developers. -
For the CSS/JSON/HTML Modules stuff, you can see the MSFT and Igalia engineers involved running the very first step of this process here: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ojwkySW-bpQ … Even an "FYI only" thread highlights lots of points the teams have to make sure they've clearly answered.
- 6 more replies
New conversation -
-
-
All of this makes sense, but I'd like to comment on something Mike said. I often see new Chrome things announced as "web" features which to me implies they are already standard, in multiple browsers, etc. It's not a web feature if it's just Chrome. Maybe that's just me though. ;)
-
This ^. I follow the standards process for many specs, and most of the people on them are clear that APIs and experimental or origin trial. My frustration has been announcements/blogs that state things as web features when they haven’t shipped. That’s the frustrating part
- 13 more replies
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.
Hullo! Friendly Standards TL & Blink API OWNER here, can answer questions about our process.