- From: Laurens Holst <lholst@students.cs.uu.nl>
- Date: Tue, 29 Mar 2005 20:52:10 +0200
- To: www-style@w3.org
Matthew Raymond wrote:
>>> A more general way however, to detect whether or not images are being
>>> load for the complete document could save a lot more issues that
>>> might come up. Something like
>>
>> That wouldn't work for me as I frequently abort pages because the images
>> are taking too long to download, which results in some images
>> displaying and
>> some reverting to the alt text.
>
> Perhaps what we need is "alt" styling...
>
> | p { background: transparent url("marble.png"); }
> | p:alt { background-color: black; }
I don’t know if that would work...
p { background: transparent url("marble1.png");
content: url("marble2.png"); }
p:alt { background-color: black; }
When will the :alt be visible, marble1.png fails to load, or
marble2.png, or both? Also, this is just about images not loading,
right? There are a limited amount of /properties/ with which you can
load images. Is it logical to ‘fix’ something done by properties with a
selector? Wouldn’t it be easier to introduce an equally limited amount
of properties for this specific functionality? Also, I think this would
then be the first selector which becomes valid based on the state of CSS
itself. What if you load an image inside an :alt selector?
Just some questions.
Replace the p with img and you’ve got an even more complex case.
OTOH, img:alt { content: attr(alt) } sounds kinda nice. Though that
wouldn’t work with XHTML 2.0.
~Grauw
--
Ushiko-san! Kimi wa doushite, Ushiko-san!!
Received on Tuesday, 29 March 2005 18:52:10 UTC