So how are we going to make sure that we don't conflict with future media
features? By having them be strings?
I was wondering because it would be nice to be able to polyfill new media
query features.
Kenneth
On Sat, Jun 1, 2013 at 10:46 AM, François REMY <
francois.remy.dev@outlook.com> wrote:
> > Do not abuse media types, use media features instead.
>
> Media features L3 can already be used without specified value, like the
> "color" feature. MQ L4 also add features like "script", "pointer" and
> "hover" which can be used likewise. It's even specified what it means:
>
> @media(x) {}
> == @media not (x:0)
> and not (x:0px)
> ... ... .......
> and not (x:none) {}
>
> That doesn't mean we shouldn't accept real pair/value to be used for
> custom MQ but simple flags are already part of the existing specs, it's not
> something created for this specific use at all.
>