- From: Christoph Päper via GitHub <noreply@w3.org>
- Date: Fri, 19 Sep 2025 14:52:51 +0000
- To: public-css-archive@w3.org
Yesterday, I assumed that the `target-…()` functions weren’t implemented anywhere and even pondered with a proposal to improve their design (by reusing `anchor-name`) in order to make adoption (by general-purpose browsers) more likely. However, as it turns out, *all* of [Vivliostyle](https://docs.vivliostyle.org/#/supported-css-features), [Prince XML](https://www.princexml.com/doc/css-props/#prop-content), [PDF Reactor](https://www.pdfreactor.com/product/doc/manual-lib.html#CrossReferences), [Antenna House Formatter](https://www.antenna.co.jp/AHF/help/en/ahf-css6.html#css3-functions), [Weasyprint](https://doc.courtbouillon.org/weasyprint/stable/api_reference.html#css-generated-content-module-level-3), [typeset.sh](https://docs.typeset.sh/setup/css-and-paged-media/page-counters#target-page-counter), [paged.js](https://pagedjs.org/en/documentation/14-supported-feature-of-the-w3c-specifications/), [BFO Formatter](https://publisher.bfo.com/live/help/#_counters_and_generated_content) actually claim to support most or all of GCPM cross reference features. I *really* wish CanIUse.com would cover PDF generators. (Sorry if I forgot one.) -- GitHub Notification of comment by Crissov Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12824#issuecomment-3312521498 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 19 September 2025 14:52:52 UTC