- From: David Woolley <david@djwhome.demon.co.uk>
- Date: Tue, 30 Mar 2004 07:28:45 +0100 (BST)
- To: www-style@w3.org
> The way to do this is NOT to introduce browser-specific code into CSS, but to
> test for support of individual features:
>
> @supports(td:hover) {
> /* CSS code */
> }
If you are going to do feature tests, the better way is an all or nothing
grouping as designs typically depend on several different features all
working as expected.
The one advantage that your approach has is that it allows more cases
to be evaluated statically. Full all or nothing processing would either
have to take a worst case assumption, or adapt to the actual structure
being styled.
Received on Tuesday, 30 March 2004 02:37:00 UTC