Generated content via URI

What is the rationale behind the change in the 2.1 April 2006 draft that
a UA is no longer required to ignore a URI resource if it cannot display
it?

Opera currently replaces an image inserted via a CSS generated content
method with the text "image" when automatic image display is disabled. I
find this behaviour most annoying.

While it may be useful for a user to be provided with a handle via which
the image can be selectively retrieved if an author has abused the
generated content mechanism to code images that should instead be coded
in the markup, the net effect of allowing this is that if widely
implemented in UAs it will only encourage authors to abuse CSS for this.

Meanwhile an author who wishes to use CSS generated content images in a
correct decorative manner, for example to display rounded box corners
for *CSS2 clients* without using markup hooks might see the totally
pointless and possibly actual content obscuring "image" replacement text
in a browser in place of what are 100% decorative images.

-- 
Spartanicus

(email whitelist in use, non list-server mail will not be seen)

Received on Sunday, 31 December 2006 19:18:27 UTC