W3C home > Mailing lists > Public > www-validator-css@w3.org > January 2014

Re: Broken Link http://jigsaw.w3.org/css-validator/nullcolors.html#propdef-background-colo r

From: Yves Lafon <ylafon@w3.org>
Date: Mon, 13 Jan 2014 06:01:37 -0500 (EST)
To: "Jukka K. Korpela" <jkorpela@cs.tut.fi>
cc: www-validator-css@w3.org
Message-ID: <alpine.DEB.2.00.1401130600230.25321@wnl.j3.bet>
On Mon, 6 Jan 2014, Jukka K. Korpela wrote:

> 2014-01-06 18:27, Yves Lafon wrote:
>
>>> Apparently, the validator is generating URLs but a crucial parameter
>>> or variable has an undefined or void value, resulting in
>>> ?http://jigsaw.w3.org/css-validator/null? instead of a proper prefix.
>> 
>> Yeah it's a known issue for CSS3, the result of going from a monolithic
>> specification to many specifications, including properties defined by
>> multiple specifications...
>> So it will work if you use css21 profile.
>
> And if I?m using CSS3 profile? It?s been the default in the CSS Validator for 
> some time, and it?s what people are using or at least moving to.
>
> I understand that fixing this would be a major effort, like a redirection 
> table that maps property names to various addresses. But the current 
> situation is rather bad, causing increased confusion.

Some properties are defined in different specs in CSS3, making the thing 
even worse!
>
> Would it be possible to switch off the link generation when CSS3 profile is 
> used? If not, even switching it off completely might be better than the 
> current situation.

Yes, as I just reworked part of the output, I took your suggestion and 
removed the link generation for profiles others than css2 and css21.
Thanks!


> Yucca
>
>
>
>

-- 
Baroula que barouleras, au tiƩu toujou t'entourneras.

         ~~Yves
Received on Monday, 13 January 2014 11:01:39 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:01:14 UTC