W3C home > Mailing lists > Public > www-style@w3.org > January 2012

Re: Feedback about @media -o-paged

From: Morten Stenshorne <mstensho@opera.com>
Date: Wed, 04 Jan 2012 16:27:45 +0100
To: Henri Sivonen <hsivonen@iki.fi>
Cc: www-style@w3.org
Message-ID: <8739bvbi8e.fsf@aeneas.oslo.osa>
Henri Sivonen <hsivonen@iki.fi> writes (Tue, 20 Dec 2011 15:16:56 +0200):

> A while ago, Opera released Opera Reader with pagination support for
> interactive screen media. @media -o-paged { ... } is used for
> targeting only the builds of Opera that have this capability--the
> capability being support for overflow: -o-paged-x;, etc.
>
> For authoring style sheets that make sense for both UAs that support
> overflow: paged-x; and UAs that don't, I think having some kind of
> at-rule mechanism for targeting rules only to UAs that support paged
> overflow is very important. However, it seems strange and conceptually
> incorrect to have a special media query medium for this.

Agreed.

> It would be more appropriate to use @supports (overflow: paged-x) {
> ... }, since conceptually the at-rule block is all about targeting
> rules to UAs that support the paged overflow feature.
>
> (Of course, without @media paged {...}, it would be an authorability
> disaster for an UA to ship with paged overflow support without also
> having @supports support.)

Since Opera hasn't implemented @supports{}, we ended up with using a
media feature for this instead. We will remove the @media -o-paged {}
thing and replace it with a boolean media feature "-o-paged", which will
evaluate to true if the UA supports the four new overflow property
values. We should probably consider switching over to @supports(){} in
the future.

-- 
---- Morten Stenshorne, developer, Opera Software ASA ----
---- Office: +47 23693206 ---- Cellular: +47 93440112 ----
------------------ http://www.opera.com/ -----------------
Received on Wednesday, 4 January 2012 15:31:24 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:48 GMT