- From: Bernhard Fey via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 Jan 2023 16:07:33 +0000
- To: public-css-archive@w3.org
bernhardf-ro has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-anchor-1][css-page] Suggestion for predefined anchor constants and paged media specific non-element anchors == We think that Anchor Positioning could cover a use case we current have to provide a proprietary property for. That use case is that in paged media it should be possible to position elements relative to the page. To achieve that via anchors we propose two additions to the specification: 1. The concept of predefined anchor constants, which can be unrelated to elements. The syntax could be an ident, without the two dashes, as it is explicitly CSS-defined not author-defined. However, we have no specific preference regarding this. 2. Defining the following constants to refer to boxes of the first page that the absolutely-positioned element has boxes on: - page-content - page-padding - page-border - page-margin - page-trim - page-bleed - page-media When the UA has no concept of trim, bleed and media, those should fall back to margin. For non-paged media these anchors could either be not found or fall back to the root element or the view port. see https://w3c.github.io/csswg-drafts/css-anchor-1/#determining https://w3c.github.io/csswg-drafts/css-page-3/#page-model Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8301 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 11 January 2023 16:07:35 UTC