The w3c mailing lists and github issues are the saddest thing. Most of the things we desperately need in the web APIs have been described as an issue at some point, years ago, but then the discussion just stops and nothing happens.
-
Show this thread
-
I'm not deeply enough involved in the standards process to really understand why it is so dysfunctional, but with the Chrome team continuing to consolidate power while being pretty deaf to problems that their bosses don't personally have, I'm not optimistic about the future.
3 replies 10 retweets 27 likesShow this thread -
I guess I can comment on at least one aspect of what goes wrong: Many issues are only observable to people writing a specific kind of client code (say, editor maintainers), but that group has access to few of the resources needed to get a proposal anywhere.
2 replies 2 retweets 8 likesShow this thread -
To write a proposal you need to know how browsers currently implement things, because specs that don't map well to that don't have a chance. Then you usually need to get it implemented. Both are outside of the skillset and beyond the time budget of people who aren't browser devs
3 replies 3 retweets 10 likesShow this thread -
Replying to @MarijnJH
Hey Marijn, I run standards for Chrome. Our general way of working is try to find folks who have a specific problem and then work with them to understand the importance of the issue and work to resolve it. Editing is a particularly gnarly area.
1 reply 0 retweets 1 like -
Replying to @slightlylate @MarijnJH
We don't need (all) web developers to become standards insiders to help make progress. Reduced test cases, http://crbug.com entries, and the like can help. The W3C is one forum where we can try to get buy-in for proposals, but it's not where you would want to start.
1 reply 0 retweets 0 likes -
Replying to @slightlylate @MarijnJH
In general, progress hinges on collaboration between engine developers and web developers. Those constituences (bounded by our need to put the user first) are the key in moving things downfield. Browser engineers can do the standards-language-lawyering for you.
1 reply 0 retweets 0 likes -
Replying to @slightlylate @MarijnJH
I tried to write up some of this here: https://infrequently.org/2018/06/effective-standards-work-part-2-threading-the-needle/ …
1 reply 0 retweets 0 likes -
Replying to @slightlylate @MarijnJH
In a nutshell, you want to find the engineers working in an area on a browser who can help prioritize your need. I can help route this one if you haven't already found the correct person via crbug.
1 reply 0 retweets 0 likes -
Replying to @slightlylate
crbug seems irrelevant for a standards shortcoming, no? Without standard, we can't expect Chrome to implement something. Issue that prompted this thread was https://github.com/w3c/selection-api/issues/57 …. But recent downscaling of Chrome's bidi support make me dubious I'll find much enthusiasm for this
1 reply 0 retweets 0 likes
Standards come *after* folks agree something is a problem and work to describe potential solutions. Don't look to standards groups for leadership, look to browsers for that. That said, you're right that staffing on this stuff can be variable.
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.