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... :(
-
-
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...
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Oh, and doing it now has even worse performance implications. So not only do we get more complex code, we get slower code all around. Yay.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
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.)
-
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.
Kraj razgovora
Novi razgovor -
Č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.