New issue
Advanced search Search tips

Issue 800985 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

Negative text-indent on inline-block won't reduce width correctly with more than one inline element

Reported by kizm...@gmail.com, Jan 10 2018

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 YaBrowser/17.10.0.2052 Yowser/2.5 Safari/537.36

Steps to reproduce the problem:
Go to https://codepen.io/kizu/pen/ZvxMoz

or

1. Create an element with width fitted to content (like inline-block)
2. Add pseudo with content containing multiple CSS counters (more than 1)
3. Add negative text-indent that would cover the width of all added symbols.

What is the expected behavior?
The element's width should be equal to zero

What went wrong?
The element's width would be equal to the number of counters minus one in characters (really strange)

Did this work before? No 

Does this work in other browsers? Yes

Chrome version: 61.0.3163.100  Channel: n/a
OS Version: OS X 10.13.2
Flash Version: 

Other browsers: Firefox and Edge render this properly.
 
Labels: Needs-Milestone
Components: -Blink>CSS Blink>Layout
Status: Untriaged (was: Unconfirmed)
Summary: Negative text-indent on inline-block won't reduce width correctly with more than one inline element (was: Negative text-indent on inline-block won't reduce width fully when multiple counters present)
Counters not necessary. See attached test.
count.html
304 bytes View Download

Comment 3 by e...@chromium.org, Jan 12 2018

Labels: -Pri-2 Pri-3
Status: Available (was: Untriaged)
Project Member

Comment 4 by sheriffbot@chromium.org, Jan 14

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
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
The bug is still reproduced and still behaves rather strangely, so it would make sense to fix it if it is possible.

Comment 6 by e...@chromium.org, Jan 17 (5 days ago)

Labels: Fixed-In-LayoutNG
Status: Available (was: Untriaged)
The good news is that this has been fixed in our new layout engine. The bad news is that it isn't ready for realize quite yet, it'll be another release or two.

Comment 7 by kizm...@gmail.com, Jan 18 (5 days ago)

Oh, that's really good news! Would gladly wait for this release.

Sign in to add a comment