Regression:Overlapping of direction is observed on google maps in print preview.
Reported by
shruti.j...@etouch.net,
Feb 6 2018
|
||||
Issue descriptionChrome Version:65.0.3325.51 (Official Build)Revision bf82f5d25853ccdc46fb63304524ca023c1b24c2-refs/branch-heads/3325@{#326} (32/64-bit) OS: Windows (7,8.1,10) ,Mac OS X(10.12.6) and Linux (14.04 LTS) Screen resolution:Windows 7 (1366*768) WINDOWS 8.1(1280*1024) Windows 10 (1920*1080) MAC (1366*7680) and Linux (2560*1760). Steps to reproduce: 1.Launch Chrome and navigate to maps.google.com 2.Set Source and Destination and choose direction click on details. 3.Click on print and choose print including maps and click on print and observe. Actual Result:Overlapping of directions is observed in print preview of maps. Expected Result: Print Preview should be proper and no overlapping of contents of arrows should be there in print preview of maps. This is Regression issue broken in ‘M-61’ and below is the bisect info: Manual Bisect: Good Build: 61.0.3155.0(Revision:485785) Bad Build: 61.0.3156.0(Revision:486205) Narrow Bisect: https://chromium.googlesource.com/chromium/src/+log/681f7bf9c909d01aca60d1c9dfa2c00ade933c8a..83733880fb55cae747c8ccf55ba0eea54168b9fd?pretty=fuller&n=10000 Suspecting: https://chromium.googlesource.com/chromium/src/+/895850e50bb21bac2b2e2dc6b555d1877f969c31 @estade: 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: 1.Unable to provide bisect using per-bisect revision, hence providing suspect using narrow bisect. 2.Issue is reproducible on above screen resolutions. 3.Issue is seen on stable/beta M64 #64.0.3282.140 and dev M65 #65.0.3325.31. Thank You!
,
Feb 6 2018
,
Feb 6 2018
,
Feb 21 2018
I've found this bug is very flaky and does not reproduce consistently. Therefore trying to bisect without taking the flakiness into consideration leads bad bisect results. |
||||
►
Sign in to add a comment |
||||
Comment 1 by shruti.j...@etouch.net
, Feb 6 2018