11 ms·
That patch would not be welcome. The patch to make the behavior intuitive is literally to remove "!important" from one CSS file. They're not changing because th
by Skalman 13y ago
That patch would not be welcome. The patch to make the behavior intuitive is literally to remove "!important" from one CSS file. They're not changing because they're afraid to break the web.
- mburns 13y ago> They're afraid to break the web. They tried a fix and it broke YouTube. So it seems like a reasonable fear. https://bugzilla.mozilla.org/show_bug.cgi?id=349259#c54 https://bugzilla.mozilla.org/show_bug.cgi?id=349259#c54 > The patch ... is literally to remove "!important" from one CSS file It isn't a simple one line fix, as Firefox developer kindly explained. https://bugzilla.mozilla.org/show_bug.cgi?id=349259#c76 https://bugzilla.mozilla.org/show_bug.cgi?id=349259#c76 >That patch would not be welcome. They describe what work would be required (and where the changes would likely be) for the patch to be accepted in the bug. https://bugzilla.mozilla.org/show_bug.cgi?id=349259#c80 https://bugzilla.mozilla.org/show_bug.cgi?id=349259#c80
- Skalman 13y agoIt's a one-line fix to make it intuitive, but that's not what's needed here. Ultimately there should be some spec so that browser vendors can converge towards a single behavior.