W3C home > Mailing lists > Public > www-amaya@w3.org > January to March 2003

Re: Amaya 7.2 Bug Report: Color names

From: Vincent Quint <Vincent.Quint@inrialpes.fr>
Date: Tue, 11 Feb 2003 18:09:58 +0100
To: Bartolomé Sintes Marco <BartolomeSintes@ono.com>
Cc: "Lista Amaya" <www-amaya@w3.org>, Vincent.Quint@inrialpes.fr
Message-Id: <20030211170958.C1F943DFD@lihue.inrialpes.fr>

Bartolomé Sintes Marco wrote:
> 
> Bug 1
> 
> Amaya displays strange colors when the name of the colors in the 
> CSS file begins with light-, medium- or pale-. 
> For example:
> h1 { background-color: light-yellow; }
> p { background-color: light-blue; }

Bug fixed. Those names are now considered as invalid color names.

> - - - - - - - - - - - - -- - 
> 
> Bug 2 (not so sure)
> 
> Amaya displays "grey" color like "gray" and "lightgray" color like "lightgrey" 
> but the correct names are only "gray" and "lightgrey", aren't they?

They are.

> "grey" and "lightgray" values are shown by Amaya and Mozilla, but are not shown 
> by Internet Explorer.

These colors are accepted by Amaya. Not sure they should be removed...

> - - - - - - - - - 
> 
> Suggestion 1
> 
> If incorrect names are written in a style attribute (for example, background-color: foofoo;),
> a warning message (Invalid color value "foofoo") is shown in the parsing error view.
> But this message is displayed only the first time the attribute is set. If the document is
> saved and reopened, the message is not displayed.
> 
> Could the parsing that detects the error be included in every opening or saving of a XHTML 
> document (or a CSS file)?

OK. Amaya behaves the way you suggest now.

> - - - - - - - - - -
> 
> Best regards,

Thanks for your comments.

> Bartolome Sintes Marco (htttp://www.mclibre.org)

Vincent.
Received on Tuesday, 11 February 2003 12:10:38 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:53:27 UTC