15033 2011-12-01 23:02:58 +0000 seamless="" should also make media queries get evaluated against the nearest ancestor non-seamless browsing context. See https://bugzilla.mozilla.org/show_bug.cgi?id=80713#c114 2012-09-28 05:19:07 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#attr-iframe-seamless P3 normal --- 1 contributor silviapfeiffer1 dbaron ian mike public-html-admin public-html-wg-issue-tracking robin public-html-bugzilla oldest_to_newest 60739 0 contributor 2011-12-01 23:02:58 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/ Multipage: http://www.whatwg.org/C#attr-iframe-seamless Complete: http://www.whatwg.org/c#attr-iframe-seamless Comment: seamless="" should also make media queries get evaluated against the nearest ancestor non-seamless browsing context. See https://bugzilla.mozilla.org/show_bug.cgi?id=80713#c114 Posted from: 2620:0:1000:147d:fa1e:dfff:fedd:ce8d by ian@hixie.ch User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_5_8) AppleWebKit/535.8 (KHTML, like Gecko) Chrome/17.0.942.0 Safari/535.8 66159 1 dbaron 2012-03-27 23:36:30 +0000 On the other hand, I've heard people request the ability to use media queries on parts of a page (particularly when designing page modules that can be reused). But that only works for queries on things that are clearly input rather than output (in general, widths as input and heights as output), and it might be hard to define how. 70426 2 contributor 2012-07-18 07:28:28 +0000 This bug was cloned to create bug 17982 as part of operation convergence. 74736 3 silviapfeiffer1 2012-09-28 05:19:07 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: applied patch https://github.com/w3c/html/commit/4ade419872cdef95fe8a55a4f0f958b163fb7465 Rationale: adopted resolution by WHATWG