Closed Bug 1172777 Opened 9 years ago Closed 9 years ago

Percentage padding applied on block in orthogonal flow (vertical writing-mode)

Categories

(Core :: Layout: Block and Inline, defect)

defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1172774
Tracking Status
firefox41 --- affected

People

(Reporter: bugzilla, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: testcase)

Tests with vendor-prefixes
--------------------------


http://www.gtalbot.org/BrowserBugsSection/CSS3WritingModes/s72-percent-padding-vrl-002.xht


http://www.gtalbot.org/BrowserBugsSection/CSS3WritingModes/s72-percent-padding-vlr-003.xht


Expected result
---------------

http://www.gtalbot.org/BrowserBugsSection/CSS3WritingModes/s71-margin-vrl-002-ref.xht


Explanation
-----------

"
The percentage is calculated with respect to the width of the generated box's containing block, even for 'padding-top' and 'padding-bottom'.
"
8.4 Padding properties
http://www.w3.org/TR/CSS21/box.html#padding-properties

div.foo
    {
      padding-bottom: 2.5%; /* 5px */
      padding-left: 50%; /* 100px */
      padding-right: 25%; /* 50px */
      padding-top: 10%; /* 20px */
      ...
    }

but the web inspector tool reports huge, weird numbers like:

padding-bottom: 447392px;
padding-left: 8947850px;
padding-right: 4473920px;
padding-top: 1789570px;


Notes
-----

- Those 2 tests used to pass in Firefox 38.0a1 buildID 20150204150323: see
http://lists.w3.org/Archives/Public/public-css-testsuite/2015Feb/0002.html
- These 2 tests have been submitted to the test.csswg.org repository 
- Chrome 40+ pass these 2 tests; Prince 9.0.5 and Prince 10.2r1 are passing the vertical-rl test (s72-percent-padding-vrl-002)
- I am using Firefox 41.0a1 buildID=20150608030201
- I use Linux 3.13.0-53-generic x86_64, Qt: 4.8.6, KDE 4.13.3; Kubuntu (trusty) 14.04.02 LTS
- I've searched for duplicates and did not find any.
Blocks: writing-mode
Keywords: testcase
Calculation of padding and margins use the same input computed in OffsetPercentBasis, so this is the same bug as bug 1172774 (but let's check in these testcases as well!)
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.