https://github.com/w3c/webappsec-feature-policy/issues/349 … just makes me so sad. First Chrome refused to remove the behavior back when Firefox didn't implement it, and removing it was web-compatible. Then we were forced to implement it for compat. Now they want to add complexity to sometimes disable it... :(
-
-
Replying to @really_bz @bz_moz
The best time to remove/attenuate quirky behavior is, indeed, several years ago. Second best is today!
3 replies 0 retweets 2 likes
Replying to @mikewest
You have no idea how much time I spent back then trying to convince y'all to remove this, and just getting stonewalled. This is _incredibly_ frustrating, especially since now we bake in EVEN MORE complexity instead of what we should have done all along...
8:33 AM - 18 Nov 2019
0 replies
0 retweets
14 likes
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.