- From: Thomas Brierley via GitHub <sysbot+gh@w3.org>
- Date: Sun, 07 Jun 2020 20:11:27 +0000
- To: public-svg-issues@w3.org
> @IanBellomy That's not really how it was/is... Imagine if all jpegs used to display differently. Someone said, wouldn't it be great if they all rendered the same. A new specification for jpegs got rid of some things that made jpegs difficult/impossible to implement. At some point all jpegs will render the same once everyone implements the new specification but a few old ones written a long time ago that always rendered differently now don't render as the author originally intended but then again on many browsers they never did. For jpeg substitute use elements and you have the history. Sorry this is not quite true either, I think a lot of confusion in this thread stems from the bundling of support for style cascade in the reference-context and instance-context together, when they can be used completely independently. So let me make it clear: Support for instance-context styling alone was supported by all major browsers since around IE9 (2011). Consistent cross browser support for a feature means it will have been used by devs, it means there is SVG content out there now which is broken. Where it gets quirky and inconsistent is support for reference-context styling and combining of the cascades. No one is contesting this fact, and it's unlikely anyone utilised it heavily for this reason because cross browser testing will have revealed those quirks. I am highly suspicious of this decision for nuking both sides of <use> styling support having more to do with the attractiveness of unifying the implementation with the shadow DOM, and so drawing a box around both was convenient if incorrect. -- GitHub Notification of comment by ThomasBrierley Please view or discuss this issue at https://github.com/w3c/svgwg/issues/367#issuecomment-640272972 using your GitHub account
Received on Sunday, 7 June 2020 20:11:29 UTC