W3C home > Mailing lists > Public > xsl-editors@w3.org > October to December 2008

[Bug 6319] New: Tables and border-separation

From: <bugzilla@wiggum.w3.org>
Date: Thu, 18 Dec 2008 10:35:40 +0000
To: xsl-editors@w3.org
Message-ID: <bug-6319-2197@http.www.w3.org/Bugs/Public/>


           Summary: Tables and border-separation
           Product: XSLFO
           Version: 1.1
          Platform: PC
               URL: http://lists.w3.org/Archives/Public/xsl-
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSL-FO
        AssignedTo: alb.w3c@gmail.com
        ReportedBy: Tony.Graham@MenteithConsulting.com
         QAContact: xsl-editors@w3.org

+++ This bug was initially created as a clone of Bug #6267 +++

+++ This is from the second half of Bug #6267. +++

Now about tables. Section 6.7.3, “fo:table” says that in the separate 
border model the border of the table is composed of half the value of 
the border-separation property plus the border as specified by the 
property. Which would mean that the border-start(trait) would, in this 
particular case, be different from the border-start(property):
    border-start(trait) = border-start(property) +
border-separation.inline-progression-dimension / 2

That’s why it seems important to me to know whether we are speaking of 
traits or properties in the formulas above. If both formulas use the 
same value (trait or property), then we have the result #1 on the 
attached picture. If formula (1) uses the trait and formula (3) uses the 
property, then the simplification will give:
    xa = start-indent + start-intrusion-adjustment
         &#8722; border-start(property) &#8722; padding-start 
         &#8722; (start-indent &#8722; border-start(trait) &#8722;
       = start-intrusion-adjustment + border-separation.i-p-d / 2
Leading to result #2 in the attached picture, which is a sensible 

And if formula (1) uses the property and formula (3) the trait, we get 
result #3 which is probably less likely to be expected.

Finally, Section 6.7.3, “fo:table” and Section 6.7.10, “fo:table-cell” 
mention the “table grid boundary line”, but it is unclear where this 
line should actually lie, especially with respect to the table padding. 
There seems to be an inconsistency since Section 6.7.3 states that “the 
first [border component], which is placed with the inside edge 
coincident with the outermost table grid boundary line, has the width of 
half the value for the ‘border-separation’ property”. And Section 6.7.10 
states that “the first [border component], which is placed with the 
outside edge coincident with the table grid boundary line, has the width 
of half the value for the border-separation trait”. Then where shall the 
padding be placed? The only consistent way to resolve this issue in my 
opinion is to make the padding coincide with the table outermost grid 
boundary line. See the attached picture as an illustration (where 
case #1 from above has been selected). It might be helpful to add an 
indication with this respect in the Recommendation.

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, 18 December 2008 10:35:48 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:44:25 UTC