Re: [csswg-drafts] [css-images] [css-gcpm] Overloaded definitions of element() (#1981)

@faceless2 wrote:

> Another solution would be to merge `element()` with `url()`, rather than with `image()`.

Obviously you only refer to the definition within CSS Images 4, not the one in CSS GCPM 3.

That idea sounds intriguing and I really like it, though reusing `url()` also has a downside. It's not feature-detectable because URLs with anchors are already valid. I.e. `background-image: url(#x);` is parsed by user agents, and therefore an author cannot use `@supports (background-image: url(#x)) { ... }` to check whether the user agent supports using an element as an image or not.

Sebastian

-- 
GitHub Notification of comment by SebastianZ
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1981#issuecomment-748680991 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Sunday, 20 December 2020 22:38:47 UTC