New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 789723 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Inline-block element irretrievably disappears in a block context with white-space: nowrap / text-overflow: ellipsis / overflow: hidden

Reported by chea...@primitybio.com, Nov 29 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36

Steps to reproduce the problem:
1. https://jsfiddle.net/de5229jw/2/

What is the expected behavior?
The inline-block element should be visible again when the block element's width returns to a size that can include the inline-block element without any overflow.

What went wrong?
The inline-block element disappears and does not render ever again even when it is given enough space, unless its display property is changed to something else and then changed back.

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 62.0.3202.94  Channel: stable
OS Version: OS X 10.13.0
Flash Version: 

If anyone has the time, I have a question regarding how the text is cut off (before the bug happens where block element's width is returned to normal): 

Chrome's behavior sets ellipses _inside_ of the inline-block element. Firefox treats it as a grapheme, which I would expect, and Safari cuts it off and only puts ellipses if the break boundary is on text.

But Chrome's behavior seems to violate that the inline-block element's rule is text-overflow: clip. I cannot figure out why it would do this.
 
I just tried BrowserStack and the issue first appears in **Chrome 61**.

Also, regarding my question about how the ellipses are applied, the behavior around Chrome 58 and earlier matches Safari and does _not_ add ellipses inside the inline-block. I think there might be another bug there, but someone that knows more should probably call that.
Labels: Needs-Triage-M62

Comment 3 by e...@chromium.org, Nov 30 2017

Owner: kojii@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 4 by kojii@chromium.org, Dec 1 2017

Cc: robho...@gmail.com
Labels: OS-Windows
Status: Fixed (was: Assigned)
Confirmed on stable 62.0.3202.94, but also confirmed this is fixed in Canary 64.0.3271.0. Thanks to someone who has fixed this, probably robhogan@?

Sign in to add a comment