- From: Alex Mogilevsky <alexmog@microsoft.com>
- Date: Mon, 17 Oct 2011 17:59:02 +0000
- To: Håkon Wium Lie <howcome@opera.com>
- CC: "www-style@w3.org" <www-style@w3.org>
± From: Håkon Wium Lie [mailto:howcome@opera.com] ± Sent: Monday, October 17, 2011 2:57 AM ± ± Also sprach Alex Mogilevsky: ± ± > When content is shown in paged presentation, is it in paged media? ± ± I think it is paged. For example, the page/column break properties should work: That can also be result of redefinition of where page breaks apply. For example currently page break is not supposed to also be a region break, but I think it should. ± > I don't know if there is a true need for ± > triggering paged media outside print preview, but having some way ± > to trigger a different stylesheet when in paged mode would make ± > sense, wouldn't it? ± ± Yes, we need a trigger for this. ± ± In Opera's experimental implementation (which I hope to release ± shortly) we support this: ± ± html { background: red } ± @media -o-paged { ± html { background: green } ± } ± ± However, I'm unsure if it should be a new media type (as above), or a new media feature, ± which could be used this way: ± ± html { background: red } ± @media (paged) { ± html { background: green } ± } ± It can be complicated when content of the paged view is in same document (when "overflow:paged" is applied to a regular div). However on an iframe it would make perfect sense. Perhaps that could be an attribute on iframe? <iframe src="foo.htm" media="print"> -- only for print preview <iframe src="foo.htm" media="paged"> -- for interactive paged view ± Another issue is what the trigger means: ± ± 1) that the UA is capable of paging (given the right values on ± 'overflow', 'height' etc) ± ± 2) that the UA is actually in some paged mode ± ± 3) that the elements selected within the block are paged, right here and now ± ± I suggest #1 (which is what we have implemented) ± ± #2 makes demands on UAs to have modes; this is probably outside of CSS' jurisdiction ± ± #3 is messy #3 doesn't have to be messy. It can mean that the element is a child or descendant of an element with "overflow:paged", or it is part of a named flow. Alex
Received on Monday, 17 October 2011 17:59:32 UTC