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
We really do just need to solve the issues we've failed to solve these last 10+ years, and FrozenArray is not that solutions.
From another subthread, here's my suggestion for an imperfect solution that is likely way better than FrozenArray and could also be done at the Web IDL level, without ECMAScript changes:https://twitter.com/othermaciej/status/1221501449206546433 …
And yes, the constructable stylesheets spec author _also_ misused it (see "hard to properly use"). I filed https://github.com/WICG/construct-stylesheets/issues/104 … on this a month and a half ago; crickets so far...
Of course that's not actually an issue in the semantics Chrome implements for FrozenArray, which don't match the IDL spec for FrozenArray. No one else implements FrozenArray at all. And saying "the API shape webidl recommends" while implementing something else is odd too. ;)
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.