-webkit-box-decoration-break causes problems with container widths. |
||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.47 Safari/537.36 Example URL: https://jsfiddle.net/s9uqr7dg/1/ Steps to reproduce the problem: 1. Go to https://jsfiddle.net/s9uqr7dg/1/ 2. In the preview panel. The four text samples on top use box-decoration-break, the four on bottom do not. What is the expected behavior? The size (shown in red) of the top four container <div>s should be equal to the size of the text. Also, text should be aligned on the left side for left-aligned text, or right for right-aligned text. What went wrong? The width of the container <div> is slightly smaller than it should be. This causes the text to be misaligned and at times drawn outside the container <div>. What appears to be happening is the <div>'s width is equal to the <span>'s width without -webkit-box-decoration-break applied. Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? No Does this work in other browsers? Yes Chrome version: 51.0.2704.47 Channel: n/a OS Version: Ubuntu 14.04 Flash Version: Shockwave Flash 22.0 r0 If you turn -webkit-box-decoration-break on or off, this change is not reflected immediately. A property affected by -webkit-box-decoration-break (padding, border-radius) must be modified to see the changes.
,
May 19 2016
This looks to be a layout issue, so removing the Blink>CSS component. To the reporter: the issue you mention with the change not being reflected immediately, do you mean by ticking/unticking in devtools? If so, this sounds like a separate issue- can you please file a separate bug with repro steps? Thanks!
,
May 20 2016
Able to reproduce this on the latest canary(52.0.2742.0) on Windows-7, Mac OS 10.11.5 and Linux Ubuntu 14.04. This is non-regression issue seen from older chrome version: 30.0.1549.0.
,
May 20 2016
,
Jun 1 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 2 2016
,
Jul 9 2016
This issue has been moved once and is lower than Pri-1. Removing the milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 18 2017
,
Apr 13 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 19 2018
|
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by tyoshino@chromium.org
, May 18 2016