Issue metadata
Sign in to add a comment
|
Whitespace changes due to https://codereview.chromium.org/2398293003 |
||||||||||||||||||||||
Issue descriptionChrome Version : M56 What steps will reproduce the problem? 1.Paste the following snippet into a web page. <li> <p>Text</p> </li> 2. Open page What is the expected result? <bullet point> Text What happens instead of that? <bullet point> Text UserAgentString: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.90 Safari/537.36
,
Nov 7 2016
Just to confirm that this is indeed my change. Marking as Needs-Bisect
,
Nov 7 2016
Able to reproduce this issue on windows 10, Ubuntu-14.04 and Mac 10.11.6 on latest chrome canary version 56.0.2909.0 Issue is broken in M55. Bisect Info: =========== Good build : 55.0.2855.0, Revision Range(417475) Bad build : 55.0.2857.0, Revision Range(417845) After executing the per-revision-bisect script, i got the following CL's between good and bad build versions ============================================ https://chromium.googlesource.com/chromium/src/+log/e46ef7309a36681bb8d59b96a9f8b6daddad3d95..668425a36f0df11b34d55753fe7d4750d47f7ab9 Unable to find the suspecting CL which caused this issue, Could anyone from dev team help us to assign this issue to the right owner.
,
Nov 7 2016
,
Nov 7 2016
If a CL cant be found that started it I will take responsibility for it. It started around the time https://codereview.chromium.org/2398293003 landed. Thank you!
,
Nov 7 2016
,
Nov 16 2016
Were you able to pin-point the change that caused this regression?
,
Nov 17 2016
I wasn't able to - bisecting failed miserably. I was able to revert my change and still see the issue. I really don't have much else to go on unfortunately.
,
Dec 2 2016
,
Dec 5 2016
Using the per-revision bisect providing the bisect results, You are probably looking for a change made after 417687 (known good), but no later than 417688 (first known bad). CHANGE-LOG URL: --------------------------------------- https://chromium.googlesource.com/chromium/src/+log/540f679169b5a26a422b182c396b31b7da34aaef..36d85fd5ae96048efcef076a209655ddf2bd02fe From the CL above, assigning the issue to the concern owner @glebl : Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner. Note: Adding RB-Stable for now, please feel free to edit if this is not the case. Thanks!
,
Dec 5 2016
,
Dec 5 2016
http://crrev.com/417688 is an intentional change that fixed a long standing interop issue. Please try to open the same html snippet in other browsers(Firefox, Edge). They all position fragment on the new line relative to marker. See W3C discussion about this issue https://lists.w3.org/Archives/Public/www-style/2015Mar/0163.html |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by nainar@chromium.org
, Nov 6 2016