- From: Sam Sneddon via GitHub <sysbot+gh@w3.org>
- Date: Fri, 01 Oct 2021 14:17:39 +0000
- To: public-css-archive@w3.org
> That's great! I guess the only risk then is use of the prefixed variant that's currently rejected but would start working and have an unintended effect. It's not super common but not a theoretical problem. WebKit did actually start treating the prefixed form identically when (unprefixed) `image-set()` was first implemented, but this was reverted in https://bugs.webkit.org/show_bug.cgi?id=206909 due to Gmail breakage. Arguably, though, the underlying cause of that is https://bugs.webkit.org/show_bug.cgi?id=231078 (invalid `<image>` renders as a broken image in WebKit). -- GitHub Notification of comment by gsnedders Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6285#issuecomment-932270632 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 1 October 2021 14:17:42 UTC