W3C home > Mailing lists > Public > www-style@w3.org > April 2005

Re: Style confirmation descriptors

From: Barry <wassercrats@hotmail.com>
Date: Fri, 8 Apr 2005 17:06:21 -0400
Message-ID: <BAY102-DAV176F94B2DEF84878287FA8B93F0@phx.gbl>
To: "Mikko Rantalainen" <mikko.rantalainen@peda.net>, <www-style@w3.org>

> That doesn't provide even close enough information to fix the problem with 
> some other CSS rules.

I misunderstood that in my last post. If you know that only one browser that 
you care about renders a webpage in a certain, incorrect way, then you could 
figure out how to fix it for that browser and have the fix applied when the 
problem is found with the style confirmation.

You could also create various browser signatures, which could act the same 
as browser sniffing, though some people here wouldn't like that. I'm still 
wondering what websites besides, alledgedly, Microsoft block webpages from 
certain browsers. That seems to be the biggest objection to browser 
sniffing.

Anyway, with my style confirmation descriptors (SCD), browser sniffing could 
be accomplished by creating a webpage that looks a different way in the 
browser you want to sniff than in other browsers that you care about 
supporting, and using the source code for that page (hopefully it's small) 
as the DisplayTry parameter. Maybe not the entire source code, depending on 
whether you're using a property with DisplayTry and whether you can produce 
the unique rendering problem in part of the actual page that you want 
rendered.. Then describe the unique feature with the "find" descriptors and 
put the special style for the bad browser in FoundReplace. 
Received on Friday, 8 April 2005 21:06:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:36 GMT