Issue metadata
Sign in to add a comment
|
[Google Places API] Development-Tool is paused after address searching
Reported by
blue.sky...@gmail.com,
Jul 18 2017
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36 Steps to reproduce the problem: 1. Open https://developers.google.com/maps/documentation/javascript/examples/places-autocomplete-addressform on Chrome and wait for browser complete loading. 2. Open development-tool, using 'Pause On Caught Exceptions' ( PauseException.PNG ) 3. Do address searching. What is the expected behavior? Dev-tool should not be paused when searching address What went wrong? Dev-tool will catch the StopIterator exception. Please see the attach image 'StopIteratorIssue.PNG' for detail. Did this work before? N/A Chrome version: 59.0.3071.115 Channel: stable OS Version: 6.3 Flash Version:
,
Jul 18 2017
It was "pause on uncaught exceptions". The point of the issue is to ask why it should throw an exception in the first place? This looks like a bug somewhere with the dev tools to Google Maps.
,
Jul 19 2017
Sorry I am not following your comment. From the screen shots and text you selected "Pause on caught exceptions". Yes it appears the code for autocomplete throws an exception that is later caught inside the autocomplete code and handled. Some programmers use exceptions for logic control it is really up to the javascript author. I believe Chrome's devtools is working correctly as the javascript written for google places API is throwing an exception.
,
Jul 19 2017
This makes sense. This issue can be rejected.
,
Jul 19 2017
,
Aug 1 2017
The NextAction date has arrived: 2017-08-01 |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by dtapu...@chromium.org
, Jul 18 2017NextAction: 2017-08-01