- From: Dave Cramer via GitHub <sysbot+gh@w3.org>
- Date: Tue, 25 Feb 2020 18:04:36 +0000
- To: public-css-archive@w3.org
As I'm investigating this, it seems that at least some implementations force a page break when a named page is invoked. The example works as expected in both PrinceXML and WeasyPrint without adding a page-break property. I think GCPM is wrong here. [CSS Pages says](https://drafts.csswg.org/css-page-3/#using-named-pages) that implementations introduce a forced page break if necessary: > The page property is used to specify a particular type of page (called a named page ) on which an element must be displayed. If necessary, a forced page break is introduced and a new page generated of the specified type. I would propose deleting the text " that also has a forced break property applied" from GCPM. -- GitHub Notification of comment by dauwhe Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3524#issuecomment-590988998 using your GitHub account
Received on Tuesday, 25 February 2020 18:04:41 UTC