[Grok-dev] Re: Best practive for browser quirks...
sebastian at urbantalk.se
Fri Nov 23 10:30:23 EST 2007
I think we should focus on handling CSS-quirks for starters. This is
where most problems occur, taking away a lot of the fun of CSS-design.
One really doesn't want to maintain several similar css-files.
Something clever here would be a great feature that would raise
21 nov 2007 kl. 20.20 skrev Martijn Faassen:
> Sebastian Ware wrote:
>> What is the best practice for handling browser quirks in a Grok
> I don't think we have one yet. I guess browser quirks fall in three
> * HTML
> * CSS
> How common are HTML-related browser quirks? We need examples there.
> CSS-related browser quirks are known to be common. One way to handle
> this would be to serve different CSS altogether based on the browser
> in question, sniffing it server-side. This has issues when you use a
> page cache though - something like Squid wouldn't be able to cache
> the css as it'd be incorrect when approached with a different
> browser unless special measures (I don't know which) are taken.
> The other way to handle CSS related browser quirks is to use a lot
> of hacks and so on to make sure that the CSS is compliant on all
> browsers. That approach would work out of the box for Grok.
> Comments? Suggestions? It's quite possible I missed particular
> problems and solution strategies. What would people want from Grok
> in this area?
> Grok-dev mailing list
> Grok-dev at zope.org
More information about the Grok-dev