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 -
Is it systemic though? For many Hotlist-Interop issues there’s only the yearly sheriffbot annoyance. (And to be clear, for this particular case there was much more outreach than a single issue.)
1 reply 0 retweets 0 likes
I'm not quite sure what the systemic situation is. Sometimes I get a quick response on interop things, sometimes there's just silence. This particular case was not a case of "no one noticed" but of sustained opposition in defense of what even at the time was clearly a bad idea.
8:56 AM - 18 Nov 2019
0 replies
0 retweets
2 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.