- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 04 Dec 2008 16:43:23 +0000
- To: xsl-editors@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6278 Summary: Border-resolution in the collapsing-border model Product: XSLFO Version: 1.1 Platform: All URL: http://lists.w3.org/Archives/Public/xsl- editors/2007AprJun/0000 OS/Version: All Status: NEW Severity: normal Priority: P2 Component: XSL-FO AssignedTo: alb.w3c@gmail.com ReportedBy: Tony.Graham@MenteithConsulting.com QAContact: xsl-editors@w3.org >From xsl-editors@w3.org: For the (cells of the) first row of a table, border-before on the fo:table and applicable fo:table-column objects play into border resolution. When the table is broken accross several pages, do they also play for the first row of each page? Or only the very first row of the table? We agreed upon yes. This means that if border-conditionality="retain" on fo:table, then it will appear on each page (if it wins in the border resolution), which would be the same behavior as in the separate-border model. But if the fo:table-header is not omitted at page breaks, how should border resolution be performed? Technically, the areas generated by the table-cell children of fo:table-header are /replicated/ on each new page, so they would have the is-first trait set to true. So assuming that the conditionality of the fo:table's border-before is "discard", should it play or not in the border resolution of table-headers on the second and following pages? -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Thursday, 4 December 2008 16:52:13 UTC