incubator-ooo-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Bug 119401] New: suspicious property fo:margin="100%" in paragraph style 'first line indent'
Date Tue, 22 May 2012 16:06:01 GMT

          Priority: P3
            Bug ID: 119401
           Summary: suspicious property fo:margin="100%" in paragraph
                    style 'first line indent'
          Severity: normal
        Issue Type: DEFECT
    Classification: Code
                OS: All
          Hardware: PC
            Status: CONFIRMED
           Version: AOO340-dev
         Component: code
           Product: xml

Created attachment 77578
Dummy text with first line indent

Unzip the attached document and look into styles.xml. Notice that the page
style "First_20_line_20_indent" has a paragraph property fo:margin="100%". This
makes no sense, because the reference for 100% is the _width_ of the parent
element, here the body. The property fo:margin is a shorthand and will be
expanded to the four margin settings for rendering. This results in setting the
top and bottom margin to the body width. The left and right margins are
overwritten with the immediately following explicit margin-left and
margin-right settings.

1. Because margin-left and margin-right are set explicitly no shorthand should
be used, but margin-top and margin-bottom should be set explicitly too. The
correct values can be found in the paragraph style itself or in the link up
chain of paragraph styles or set to default "0cm".

2. The value "100%" should not be used at all, because the reference is the
width of the parent element, which never can be the right value for margins.

The error becomes obvious, when you export the document to XHTML. The export
filter translates the fo:margin property to the corresponding css, which
results in a wrong rendering. But the bug is not in the filter, it is already
in the odt-file.

This error might be introduced with the fix for issue 117001. For example in
DEV300m70 this error does not exist.

You are receiving this mail because:
You are the assignee for the bug.

View raw message