- From: rocallahan via GitHub <sysbot+gh@w3.org>
- Date: Wed, 28 Mar 2018 11:10:39 +0000
- To: public-css-archive@w3.org
I thought I mentioned this on www-style a few years ago but I can't find it now: I had come to the conclusion that the way to resolve this issue was to unify the image-loading path with the element-reference path, basically by eliminating the latter. You would use the image-loading path, and if you happened to load an SVG image and the fragment reference points to the right kind of element, you would use that instead of rendering the image. Document self-references would of course be special-cased. This depends on the browser being able to "punch through" the image-loading-and-rendering abstraction to access the underlying DOM, but I guess that's not a problem in practice. -- GitHub Notification of comment by rocallahan Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/383#issuecomment-376849466 using your GitHub account
Received on Wednesday, 28 March 2018 11:10:41 UTC