Absolutely positioned elements positioned incorrectly in vertical writing mode if it is over-constrained
Reported by
babata...@gmail.com,
Jan 6 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2973.0 Safari/537.36 Example URL: http://test.csswg.org/harness/test/css-writing-modes-3_dev/single/abs-pos-non-replaced-vrl-088/format/html5/ Steps to reproduce the problem: 1. Install Ahem font (it can be downloaded from https://www.w3.org/Style/CSS/Test/Fonts/Ahem/ ) 2. Run any of following tests http://test.csswg.org/harness/test/css-writing-modes-3_dev/single/abs-pos-non-replaced-vrl-088/format/html5/ http://test.csswg.org/harness/test/css-writing-modes-3_dev/single/abs-pos-non-replaced-vrl-220/format/html5/ http://test.csswg.org/harness/test/css-writing-modes-3_dev/single/abs-pos-non-replaced-vrl-224/format/html5/ What is the expected behavior? The "Test Case" tab matches to the "Reference Page". What went wrong? It does not match. The sources of the test cases describe more details in comments. http://test.csswg.org/suites/css-writing-modes-3_dev/nightly-unstable/html/abs-pos-non-replaced-vrl-088.htm http://test.csswg.org/suites/css-writing-modes-3_dev/nightly-unstable/html/abs-pos-non-replaced-vrl-220.htm http://test.csswg.org/suites/css-writing-modes-3_dev/nightly-unstable/html/abs-pos-non-replaced-vrl-224.htm Does it occur on multiple sites: N/A Is it a problem with a plugin? N/A Did this work before? No Does this work in other browsers? N/A Chrome version: 57.0.2973.0 Channel: canary OS Version: 10.0 Flash Version: Shockwave Flash 24.0 r0
,
Jan 10 2017
,
Jan 11 2017
Thanks for the report. Able to reproduce the issue on Win 10, Mac OS X 10.12.2, Ubuntu 14.04 using Chrome Canary #57.0.2977.0 & Stable #55.0.2883.87. This is non-regression issue, issue existing from M30 build, #30.0.1549.0 Observed 'Test case' tab does not match with 'Reference' tab. Please find the attached screenshot for reference.
,
Jan 25 2017
I believe this issue should be resolved as a DUPLICATE of issue 505151 or it should be merged with issue 505151 .
,
Feb 16 2017
Root cause is that LayoutBox::computeInlineStaticDistance and LayoutBox::computeBlockStaticDistance compute static position by walking up the ancestor chain assuming all ancestors are in the same writing mode.
,
Feb 21 2017
Removed the label Needs-Triage-M57 label as its already triaged in commnet # 3.
,
Feb 21 2017
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by babata...@gmail.com
, Jan 6 2017