- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Fri, 27 Mar 2009 11:48:09 -0500
- To: Andrew Fedoniouk <news@terrainformatica.com>
- Cc: Bert Bos <bert@w3.org>, "www-style@w3.org list" <www-style@w3.org>
On Fri, Mar 27, 2009 at 11:35 AM, Andrew Fedoniouk
<news@terrainformatica.com> wrote:
> I have invented ':incomplete' state flag and pseudo-class for fall-back
> cases.
> It is "on" if some data requested by the DOM element is not loaded yet.
> "Component" here is an image background or foreground (image of <img>
> element) or content of the <frame> for example.
>
> Thus you could have
>
> #with-fancy-border
> {
> border-image: ....;
> border-width: 10px;
> }
>
> #with-fancy-border:incomplete
> {
> border: 2px solid red;
> }
>
> Another state flag and pseudo-class named ':busy' is "on" if
> element's "data request queue" is not empty - it is still loading
> something.
>
> Beside of handling "border-image-is-not-available" case
> these two allow to style cases like "img data is not available"
>
> img:incomplete
> {
> background-image:url(for-img-not-found.png);
> width:xx;
> height:yy;
> }
> img:incomplete:busy
> {
> background-image:url(that-spinning-thing.apng);
> }
That'd certainly work for me. So the :incomplete state can be based
off of CSS-triggered data loads too?
~TJ
Received on Friday, 27 March 2009 16:48:52 UTC