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

Issue 726583 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Jul 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Incorrect position of list marker below a float

Reported by kwk...@vivliostyle.com, May 26 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:55.0) Gecko/20100101 Firefox/55.0

Steps to reproduce the problem:
1. Open the attached test case

What is the expected behavior?
The list marker should be on the left side of the list content ("list")

What went wrong?
The list marker is far right to the list content.

Did this work before? No 

Does this work in other browsers? Yes

Chrome version: 58.0.3029.110 (Official Build) (64bit)  Channel: stable
OS Version: OS X 10.12
Flash Version: Shockwave Flash 24.0 r0
 
list-marker-float.html
395 bytes View Download
list-marker-float-bug.png
8.4 KB View Download
Cc: nyerramilli@chromium.org
Labels: Needs-Miilestone OS-Linux OS-Windows
Status: Untriaged (was: Unconfirmed)
Thanks for the report.

Able to reproduce the issue on Win10, Mac OS X 10.12, Ubuntu 14.04 using Chrome Stable 58.0.3029.110, Canary #60.0.3111.0.

this is a non-regression issue, existing from M30 #30.0.1549.0


726583.jpg
576 KB View Download

Comment 2 by e...@chromium.org, May 26 2017

Owner: robho...@gmail.com
Status: Available (was: Untriaged)
Thank you for working on this!
Has this issue been finished by the patch?
Do you happen to have time estimate for when the fix is shipped in which channel?
Labels: Merge-Request-60
Project Member

Comment 6 by sheriffbot@chromium.org, Jun 2 2017

Labels: -Merge-Request-60 Hotlist-Merge-Approved Merge-Approved-60
Your change meets the bar and is auto-approved for M60. Please go ahead and merge the CL to branch 3112 manually. Please contact milestone owner if you have questions.
Owners: amineer@(Android), cmasso@(iOS), josafat@(ChromeOS), bustamante@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 7 by bugdroid1@chromium.org, Jun 2 2017

Labels: -merge-approved-60 merge-merged-3112
The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/e77ecceef64cb7e406b02d37953eccb3a6715fbb

commit e77ecceef64cb7e406b02d37953eccb3a6715fbb
Author: Robert Hogan <robhogan@gmail.com>
Date: Fri Jun 02 09:20:50 2017

List markers should only avoid floats on their own line.

TBR=robhogan@gmail.com

(cherry picked from commit fc0213148ed03241f5480b039bba5d2b8ae3e831)

Bug:  726583 
Change-Id: I4bec94e9034b00b4328f5c2c33c2fa95d0d83698
Reviewed-on: https://chromium-review.googlesource.com/517822
Commit-Queue: Emil A Eklund <eae@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#475574}
Reviewed-on: https://chromium-review.googlesource.com/522683
Reviewed-by: Robert Hogan <robhogan@gmail.com>
Cr-Commit-Position: refs/branch-heads/3112@{#110}
Cr-Branched-From: b6460e24cf59f429d69de255538d0fc7a425ccf9-refs/heads/master@{#474897}
[add] https://crrev.com/e77ecceef64cb7e406b02d37953eccb3a6715fbb/third_party/WebKit/LayoutTests/fast/lists/list-marker-avoid-float-expected.html
[add] https://crrev.com/e77ecceef64cb7e406b02d37953eccb3a6715fbb/third_party/WebKit/LayoutTests/fast/lists/list-marker-avoid-float.html
[modify] https://crrev.com/e77ecceef64cb7e406b02d37953eccb3a6715fbb/third_party/WebKit/Source/core/layout/LayoutListMarker.cpp

Labels: TE-Verified-M60 TE-Verified-60.0.3112.20
Verified this issue on Ubuntu 14.04, Windows-10 and Mac OS 10.12 using chrome latest dev M60-60.0.3112.20 by following steps mentioned in the original comment. Observed the list marker is seen on left side of the list content as expected. Hence adding TE-Verified label.
726583.png
114 KB View Download

Comment 9 by robho...@gmail.com, Jul 30 2017

Status: Fixed (was: Available)
Though the original testcase has been fixed,
it seems that a slightly modified testcase still exhibits the same problem.
I attached a new testcase where I simply removed 'clear: left' on the ul element.
list-marker-float2.html
437 bytes View Download
list-marker-float2-bug.png
7.8 KB View Download
Looks OK to me.
Aug 1 2017 7-13 PM.webm
957 KB View Download
I still see the problem on Chrome 60.0.3112.78 and 62.0.3173.0, both on macOS 10.12.6.
A weird point is that the problem exists just after loading the HTML file, it disappears when the window size is changed.
bd2a08da-c943-442b-ycd1-4a15f0822151.webm
4.5 MB View Download
2c3585da-1f45-468c-y9ba-1dd5b3e480aa.webm
4.0 MB View Download
OK, I can reproduce your results when I put the test on https://jsfiddle.net/u2a1x1Lx/ and throttle the network connection.

Can you reproduce it even when the test is a local html file?
As you can see from my screencast, I reproduced it with a local HTML file.
I tried Chrome 60.0.3112.90 on CentOS 7 and it did not reproduce, which agrees with your screencast.
Project Member

Comment 15 by bugdroid1@chromium.org, Aug 14 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/cd7e6cfdc27d56c2a1ed52bd802aad7b5e11e8d5

commit cd7e6cfdc27d56c2a1ed52bd802aad7b5e11e8d5
Author: Robert Hogan <robhogan@gmail.com>
Date: Mon Aug 14 23:21:22 2017

List markers should only avoid floats on their own line.

We used to update the offset of list markers after we had laid out the line
but this resulted in the list marker avoiding floats that came
after it in layout (https://codereview.chromium.org/2553793003).

PositionListMarker() always happens after a layout of the list item so it's reasonable
to always update the offset when laying one out. We can do better than this
though and only update the offset when we know there's a float to avoid, so do
that instead. The layout of a list marker consists simply of finding its offset
and updating its margins so it's cheap enough to treat a layout as an update to
the offset.

Bug:  726583 , 753099
Change-Id: I5aca82ae654f1ddece448fc89563f90b801d1110
Reviewed-on: https://chromium-review.googlesource.com/602352
Commit-Queue: Emil A Eklund <eae@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#494238}
[add] https://crrev.com/cd7e6cfdc27d56c2a1ed52bd802aad7b5e11e8d5/third_party/WebKit/LayoutTests/fast/lists/list-marker-avoid-float-2-expected.html
[add] https://crrev.com/cd7e6cfdc27d56c2a1ed52bd802aad7b5e11e8d5/third_party/WebKit/LayoutTests/fast/lists/list-marker-avoid-float-2.html
[add] https://crrev.com/cd7e6cfdc27d56c2a1ed52bd802aad7b5e11e8d5/third_party/WebKit/LayoutTests/fast/lists/list-marker-avoid-float-3-expected.html
[add] https://crrev.com/cd7e6cfdc27d56c2a1ed52bd802aad7b5e11e8d5/third_party/WebKit/LayoutTests/fast/lists/list-marker-avoid-float-3.html
[modify] https://crrev.com/cd7e6cfdc27d56c2a1ed52bd802aad7b5e11e8d5/third_party/WebKit/Source/core/layout/LayoutBlock.cpp

Has this fix landed?
I still see the same problem shown in my screencasts in comment #12 on Chrome 62.0.3202.62 and 64.0.3248.0 on macOS 10.12.6.
Is there any update on this?
I still see the same problem on Chrome 62.0.3202.94 and 64.0.3265.0 on macOS 10.12.6.

Comment 18 by phistuck@gmail.com, Nov 14 2017

#17 - it was merged to Chrome 60, so you might be looking at a new issue.
Please, look for a non-fixed issue and if you cannot find one, file a new issue and attach a small reproduction (a small HTML file that reproduces the issue).
You can comment here with the issue number.
Thank you for your response.
The issue I am seeing is the same as I reported on comments #10, #12 and I do not have any additional information, but I can file a new issue for that if it helps.

Comment 20 by phistuck@gmail.com, Nov 14 2017

#19 - I think it would be best to make sure there is an open (non-fixed) issue for that, or create one, yes.
I tried to find a non-fixed issue with "list marker" keywords but could not find one, so filed a new issue:
https://bugs.chromium.org/p/chromium/issues/detail?id=784793

Sign in to add a comment