On 2/2/11 8:57 PM, Antony Kennedy wrote:
> Which is a shame - because it's the only pure CSS method. Unless you know another?
There isn't one. There have been several proposals for
feature-detection methods in the past, though.
>> 1) Can be parsed without knowing anything about this thing you don't support.
>
> Currently, if a media feature is not known, the entire media query evaluates to "not all". This does not seem a very future-proof methodology. It would make more sense for that single media feature to evaluate to zero - i.e. false. Negating that with a local "not" would work well.
That's not future-proof either. Say we had this system. Assume a new
feature called "interactive" is introduced which is true for interactive
media. With your proposal, |not interactive| would test true in all
existing browsers that haven't been updated to support this feature,
which seems undesirable (since in fact they _are_ interactive)....
>> 2) Is guaranteed to be a boolean support check.
>
> This is true. Perhaps something like:
>
> @media screen and (supports:property)
>
> and
>
> @media screen and (doesnotsupport:property)
>
> â€¦works better?
I believe that sort of thing has been proposed in the past, yes....
-Boris