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

Issue 795583 link

Starred by 4 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Text positioning fails when long non breaking text contains tags

Reported by d...@alternet.gr, Dec 17 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0

Steps to reproduce the problem:
1. create a very long line of text without spaces (eg 80k characters)
2. duplicate the above line
3. in the duplicated line insert any tag which should not normally interrupt the continuity of the text

What is the expected behavior?
The two lines should be of equal length when viewed in the browser

What went wrong?
The lines are of different length, text positioning starts failing immediate after the tag, resulting of different text line lengths

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 63.0.3239.108 (Official Build) (64-bit)  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 27.0 r0
 
problemDemo2.html
156 KB View Download
error.png
21.8 KB View Download

Comment 1 by gov...@chromium.org, Dec 17 2017

Cc: ranjitkan@chromium.org pbomm...@chromium.org brajkumar@chromium.org
Labels: Needs-Triage-M63
Components: Blink>CSS
Labels: FoundIn-64 Target-65 FoundIn-65 FoundIn-63 Needs-Bisect OS-Linux OS-Mac
Chrome Channels where this issue is reproducible : Stable, Beta , Dev and Canary.
Does this reproducible on older versions of Chrome stable : Yes(M62,M61 and M60 still need to bisect)


Note : .
-Other browsers works fine I see this behavior only on Chrome.

 
AndroidManifest.xml
12.3 KB View Download

Comment 4 by woxxom@gmail.com, Dec 18 2017

Bisect info: 275859 (good) - 275865 (bad)
https://chromium.googlesource.com/chromium/src/+log/1b843376..90afd1ba?pretty=fuller
Suspecting https://crrev.com/323563005 "Enable DirectWrite by default"
Landed in 37.0.2042.0

Confirmed by disabling chrome://flags/#disable-direct-write and observing the bug is gone.
Note, this flag is no longer present in the official Chrome/Chromium.
Able to reproduce the issue on reported chrome version 63.0.3239.108 and on the latest canary 65.0.3297.0 using windows 10, Ubuntu 14.04 and Mac 10.13.1. As the issue is seen from M(50) 50.0.2661.0 considering it as non-regression and marking it as Untriaged.
Cc: sc00335...@techmahindra.com viswatej...@techmahindra.com
Labels: -Needs-Bisect M-65
Status: Untriaged (was: Unconfirmed)
Components: -Blink>CSS Blink>Layout
Looks like a layout issue.

Comment 8 by e...@chromium.org, Dec 20 2017

Cc: kojii@chromium.org
Status: Available (was: Untriaged)
I suspect we hit the TextNode max length.

Comment 9 Deleted

Sign in to add a comment