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.
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.
-
-
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.
-
I tried to write up some of this here: https://infrequently.org/2018/06/effective-standards-work-part-2-threading-the-needle/ …
- 3 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.