How Web Standards Work 1. design a flawed API (it's fine! APIs are hard) 2. ship it in the most-used browser, despite objections 3. get cross-browser working group to fix the API 4. oops, too late, that would break the webpic.twitter.com/IuU6Xxzilv
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
They're shipped to stable Chrome (and many Chromium embedders enable them too).
As the person who runs standards for Chrome, can you please explain how the fuck a non-standard feature got shipped to Stable Chrome?
We often lead, balancing risk/reward rather than demanding a particular point in an arbitrary process. https://www.chromium.org/blink/launching-features … Leadership is rather the point of having an engine team, after all.
Why is "team web" making me feel like we are back to IE6 again? Also, is it just me or this only happens with JS. CSS people seem to work with standards, not against them. It's Shadow Dom v0 again.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.