Incorrect intrinsic width measurement when we have two adjacent whitespace-only textframes

NEW
Unassigned

Status

()

3 years ago
7 months ago

People

(Reporter: cuihao.leo, Unassigned)

Tracking

({parity-chrome, parity-edge, parity-ie})

Trunk
parity-chrome, parity-edge, parity-ie
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(3 attachments)

(Reporter)

Description

3 years ago
Created attachment 8676325 [details]
test.html

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 Firefox/41.0
Build ID: 20151015193503

Steps to reproduce:

The attachment test.html is a simple HTML to reproduce.
Save and open it. It requires jquery to work.

Notice that there is a comment after first "span.t-zh".

Mozilla Firefox 41.0.2 on Arch Linux x86_64 with latest packages.


Actual results:

At the end of the first "a" element, an line break is incorrectly inserted. If you remove the comment in the HTML, or remove jquery hide operation, the line break will disappear.


Expected results:

The newline should not be there I think. I've test on Chromium and some webkit-based browser, there is no line break.

Comment 1

3 years ago
Created attachment 8676346 [details]
testcase

Updated

3 years ago
Component: Untriaged → Layout
Version: 41 Branch → Trunk

Updated

3 years ago
Whiteboard: [parity-Chrome][parity-Edge][parity-IE]
Created attachment 8676351 [details]
Testcase showing the issue is really the two adjacent whitespace textframes, not the comment per se
Status: UNCONFIRMED → NEW
Component: Layout → Layout: Text
Ever confirmed: true
Summary: HTML comment adds new line break oddly → Incorrect intrinsic width measurement when we have two adjacent whitespace-only textframes
Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.)
Keywords: parity-chrome, parity-edge, parity-ie
Whiteboard: [parity-Chrome][parity-Edge][parity-IE]
You need to log in before you can comment on or make changes to this bug.