- From: Bernhard Fey via GitHub <sysbot+gh@w3.org>
- Date: Wed, 08 Mar 2023 16:14:08 +0000
- To: public-css-archive@w3.org
We agree that option 2 is probably more useful to authors than option 1. It would be the same as our previous suggestion, but searching forward and picking the first box of the found element, right? We don't consider options 3 or 4 viable. However, we would like to propose one, that would cover both examples by combing options 1 and 2: 5. First go up the DOM tree until you find an element that has boxes. If it has boxes on the earlier of the 2 prospective pages but not the later one, search backwards, like in option 1. If it has boxes on the later page but not the previous one, search forwards, like in option 2. Otherwise use the default direction (probably forwards, but would have to be discussed). This way well-structured documents should work as expected in a vast majority of cases. Also it would implicitly eliminate edge-cases of options 1 and 2, where the assignment could end up before the first or after the last page, assuming that one of the two ifs is automatically satisfied if one of the two pages does not exist. _On the topic of `start`_: For PDFreactor we consider a box to be the beginning/first of a page when it is the first fragment of it's element and is in the first branch of the box tree inside it's page's content (plus some details like ignoring siblings that collapse through). That same condition could be applied to the box found by searching as in options 2 or 5. -- GitHub Notification of comment by bernhardf-ro Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8404#issuecomment-1460437894 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 8 March 2023 16:14:10 UTC