History becomes unusable after using any online map program due to flooding
Reported by
jidanni@gmail.com,
Mar 6 2018
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.119 Safari/537.36 Steps to reproduce the problem: 1. Browse a mapping program, e.g., https://www.openstreetmap.org/ https://maps.google.com/ 2. Move the map around a little, and a little more, and some more. 3. Now click History (^H) What is the expected behavior? What went wrong? History is flooded with the URL of each minor map movement, so much so that it soon becomes unusable. Did this work before? No Chrome version: 64.0.3282.119 Channel: n/a OS Version: Flash Version: Please figure out some better way.
,
Mar 7 2018
Thanks for filing the issue! Unable to reproduce the issue on reported chrome version 64.0.3282.119 using Ubuntu 14.04 with the below mentioned steps. 1. Launched chrome 2. Navigated to https://www.openstreetmap.org/ 3. Moved the map, zoomed in and out We observed only one entry in the history. @Reporter: Could you please check the same in a fresh profile with out any apps and extensions and let us know if the issue still persists. Providing the screen shot explaining the issue helps us in triaging it in a better way.
,
Mar 7 2018
OK try https://maps.google.com/ and every time you grab the map by pressing the left button and dragging, remember to release it. Each release will generate a new URL as we are now at a new latitude and longitude. Same in fact for OSM. And in fact also for each zoom and unzoom. The key is when checking history, be sure to kill the old History window first, else it will seem to not update,
,
Mar 7 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 15 2018
Able to reproduce the issue on Mac 10.13.3, Win-10 and Ubuntu 17.10 using chrome stable version #66.0.3359.170 and latest canary #68.0.3430.0. This is a non-regression issue as it is observed from M60 old builds. Hence, marking it as untriaged to get more inputs from dev team. Thanks...!! |
||||
►
Sign in to add a comment |
||||
Comment 1 by ajha@chromium.org
, Mar 6 2018