|
@bz_moz | |||||
|
github.com/w3c/webappsec-… 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... :(
|
||||||
|
||||||
|
Mike West
@mikewest
|
18. stu |
|
The best time to remove/attenuate quirky behavior is, indeed, several years ago. Second best is today!
|
||
|
|
||
|
Boris
@bz_moz
|
18. stu |
|
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...
|
||
|
|
||