- From: David Baron via GitHub <sysbot+gh@w3.org>
- Date: Tue, 20 Sep 2016 09:53:38 +0000
- To: public-css-archive@w3.org
So this isn't quite as straightforward as things that depend on writing modes, since it is possible for whether you're treating something as being on a left or right page changes which page it's on. For example, if you have an element with <code>overflow:hidden</code> (or some other element that establishes a BFC, like with <code>[display: flow-root](https://drafts.csswg.org/css-display-3/#valdef-display-flow-root display:flow-root)</code>) that is next to a float, then different combinations of margins that are changed as a function of whether the element is on a left or right page could control whether the element can fit next to the float or is pushed down below the float. I think in these cases you'd need to specify that any such cycles are broken by pushing the element to the later page. > The question is not screen vs paper, it is paginated vs not paginated. It is not the majority case, on-screen and paginated does exist. However, there are paginated displays that don't have a obvious inside/outside pages, e.g., if you're paginating on a screen. You can simulate it by just assuming the first page is a right page (or left page), but you might or might not want to. -- GitHub Notification of comment by dbaron Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/255#issuecomment-248256147 using your GitHub account
Received on Tuesday, 20 September 2016 09:53:45 UTC