W3C home > Mailing lists > Public > public-css-archive@w3.org > November 2017

[csswg-drafts] [CSS-images\ Specify fallback behavior when replaced or background image content not available

From: Chris Harrelson via GitHub <sysbot+gh@w3.org>
Date: Tue, 14 Nov 2017 20:52:39 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-273938646-1510692758-sysbot+gh@w3.org>
chrishtr has just created a new issue for https://github.com/w3c/csswg-drafts:

== [CSS-images\ Specify fallback behavior when replaced or background image content not available ==
There appears to be no spec language for what paints to the screen when the replaced content
of an <img> or CSS backgroud image is not available at paint time, either due to being in process
of being loaded, or due to an async decode.

Image fallbacks appear to be (partially?) specified in the presence of the image() function as part of
css images level 4. https://www.w3.org/TR/css-images-4/#image-fallbacks. This needs to be
extended more generally.

I think the best behavior is to fall back to whatever content painted underneath the paint phase that
would have drawn the image. e.g. if step 1.2. or step 7.1 of the algorithm below had no image content,
still paint but just skip those steps.
https://www.w3.org/TR/CSS2/zindex.html


See also https://github.com/whatwg/html/issues/1920

@vmpstr @tabatkins 

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1984 using your GitHub account
Received on Tuesday, 14 November 2017 20:52:42 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 14 November 2017 20:52:44 UTC