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.
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.
-
-
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
-
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.
End of conversation
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.