- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Mon, 16 Apr 2018 21:57:52 +0000
- To: public-css-archive@w3.org
> Option 2 is probably bad because that's not how fragment identifiers work in any other situation.
Note that it *is* how unknown fragments work in [`image()`](https://drafts.csswg.org/css-images-4/#image-fragments), so that authors can get similar backwards-compatible behavior to how property fallback works. For example, you can do `image("foo.jpg#newFragType(bar)", "manuallyApplied.jpg")`, falling back to the "manuallyApplied.jpg" image if the first either doesn't load or the UA doesn't understand the fragment type.
--
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2566#issuecomment-381763336 using your GitHub account
Received on Monday, 16 April 2018 21:58:00 UTC