W3C home > Mailing lists > Public > www-archive@w3.org > January 2004

Re: cannot validate Tantek's Mid Pass Filter hack

From: Tantek Çelik <tantek@cs.stanford.edu>
Date: Sat, 10 Jan 2004 13:29:01 -0800
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Cc: <www-archive@w3.org>
Message-ID: <BC25ADEC.33B6F%tantek@cs.stanford.edu>

On 1/10/04 2:17 AM, "Bjoern Hoehrmann" <derhoermi@gmx.net> wrote:

> * Tantek Çelik on <http://www.w3.org/Bugs/Public/show_bug.cgi?id=363>
>> When it was last updated/published on 2003-10-13, the mid pass filter page
>> validated against the CSS validator without any errors or warnings.
> 
> Apart from the import loop bug (which seems to be fixed now), the style
> sheet at http://tantek.com/CSS/Examples/highpassfilter.css is actually
> invalid. As per CSS 2.0, @import must be followed by a URI as a string
> or inside the url(...) notation,

No, per CSS2(.1) grammar[1] and prose[2], @import may be followed by a
*string* which is then interpreted as a URI.  Nowhere in CSS is it required
that the string be a valid URI -- user agents are only expected to be able
to parse it as string.  Thus the style sheet is still valid CSS.

The only thing that the validator was complaining about was the MIME type of
the null?{ file which I believe I have fixed but am unable to check because
the CSS validator is timing out when attempting to read any HTTP resources
(like I tried CSS validating http://yahoo.com for example so I know it is
not a problem with my web server.)

> <null?"{> however is no legal URI since
> '"' and '{' are excluded from the URI syntax (section 2.4.3. of RFC2396)

That certainly appears to be so.  I'll investigate an alternative with a
valid URI.

Tantek

[1]
 http://www.w3.org/TR/2003/WD-CSS21-20030915/grammar.html

[2]
 http://www.w3.org/TR/2003/WD-CSS21-20030915/cascade.html#at-import
Received on Saturday, 10 January 2004 16:29:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 7 November 2012 14:17:39 GMT