On 12/23/18 2:59 AM, Emilio Cobos Álvarez wrote:
Summary: More explicitly expose the kind of handling for overflowing content in media queries. Using
a media expression instead of the print media type allows for more flexibility, see the bug
description.
Implementation wise, we already expose the same kind of information via @media print right now,
given we don't have any kind of built-in EBook mode or something like that.
A volunteer sent patches for this, and I see no reason not to take them, unless somebody objects
here. Thanks a lot quasicomputational@! :)
Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1422235
Link to standard:
https://drafts.csswg.org/mediaqueries-4/#mf-overflow-inline
https://drafts.csswg.org/mediaqueries-4/#mf-overflow-block
Platform coverage: all
Estimated or target release: 66
Preference behind which this will be implemented: None
Is this feature enabled by default in sandboxed iframes: Yes
DevTools bug: N/A, existing devtools features should cover this.
Do other browser engines implement this? No, we'd be the first ones implementing this part of the
spec, but I think it's uncontroversial. The spec author was the one that filed the bug requesting
implementation, so spec-wise the feature should be stable as well.
General CSSWG policy is that any spec in CR has the consensus of the CSSWG
to be implemented and shipped.
“Once a specification reaches the Candidate Recommendation stage,
implementers should release an unprefixed implementation of any
CR-level feature they can demonstrate to be correctly implemented
according to spec, and should avoid exposing a prefixed variant
of that feature.” -- https://www.w3.org/TR/CSS/#testing
Media Queries Level 4 is in CR, so anything there is good to go.
~fantasai
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
