search

AntennaHouse / focheck

XSL-FO validation using RELAX NG and Schematron.
Apache License 2.0
31 stars 7 forks source link

span="all" only effective in fo:flow context #35

Closed michael-aka-mmh closed 7 years ago

michael-aka-mmh commented 7 years ago

As I learned via AH support:

span="all" behavior in static area's is a known limitation. The xsl-fo standard restricts the use of this property to elements that are descendants of fo:flow.

So, I assume a warning could be added via Schematron rule.

https://www.w3.org/TR/xsl/#span

tgraham-antenna commented 7 years ago

So how many of these are deserve a warning?

        <fo:static-content flow-name="xsl-region-before">
            <fo:block-container span="none"></fo:block-container>
            <fo:block-container span="all"></fo:block-container>
            <fo:block-container span="inherit"></fo:block-container>
        </fo:static-content>
michael-aka-mmh commented 7 years ago

Hi Tony, as far as I understand the spec, that would be "none" and "all".

tgraham-antenna commented 7 years ago

"none" is the initial value that doesn't cause spanning. Since span has no effect in fo:static-content, I added a warning for when the attribute is present.