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... :(
-
-
Odgovor korisniku/ci @bz_moz
The best time to remove/attenuate quirky behavior is, indeed, several years ago. Second best is today!
0 proslijeđenih tweetova 2 korisnika označavaju da im se sviđa
Odgovor korisniku/ci @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...
08:33 - 18. stu 2019.
0 replies
0 proslijeđenih tweetova
13 korisnika označava da im se sviđa
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.