3 ms·
> I don’t think it will surprise you to learn that handling legacy browser quirks is a common theme in the UA stylesheet. That's the last place I'd expect lega
by SahAssar 5y ago
> I don’t think it will surprise you to learn that handling legacy browser quirks is a common theme in the UA stylesheet.
That's the last place I'd expect legacy hacks. The UA stylesheet runs in the exact browser and version it was designed for, why does it need legacy support?
Or am I misunderstanding the paragraph and it's really about emulating legacy browser behavior?
- sitharus 5y agoIt’s not legacy behaviour for Safari, it’s legacy behaviour for the web. Browsers support all sorts of issues created by old browsers and loose html specs - see the comment about the special value to centre text like Netscape 4 did.
- SahAssar 5y agoThat's why I added the question saying "Or am I misunderstanding the paragraph and it's really about emulating legacy browser behavior?" Still feels to me like that would be the last place to require apple-specific properties or variables, since if it emulates old browsers it should not ever change, right?
- sitharus 5y agoThey use Apple-specific properties because these are non-spec behaviours that nobody should be using. Since there’s no official way of invoking these legacy behaviours they’re placed behind vendor properties. Firefox does the same thing.