Debugger breakpoints ignored after creating overrides.
Reported by
joseph.c...@joomsavvy.com,
Apr 1 2018
|
||||
Issue description
Chrome Version : 65.0.3325.181
OS Version: 6.3
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari:
Firefox:
IE/Edge:
What steps will reproduce the problem?
1.set up overrides
2.change javascript and save
3.reload page
What is the expected result?
Debugger stops at breakpoints normally.
What happens instead of that?
Debugger stops at a random point and disregards all breakpoints.
Please provide any additional information below. Attach a screenshot if
possible.
UserAgentString: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36
,
Apr 3 2018
Thanks for filing the filing the issue! Checked the issue on reported chrome version 65.0.3325.181 using Mac 10.13.1 with the below mentioned steps. 1. Launched chrome 2. Inspected the page 3. Opened Overrides in sources tab. It resulted in "+ Select folder for overrides". @joseph.cardwell: As we are not very clear on which folder to be taken for override, Could you please share a sample test file/URL which helps us to triage the issue in a better way. And also please let us know whether the process followed by us is correct. Tentatively adding component "Platform>DevTools", please change if this isn't apt.
,
Apr 3 2018
You have to select a local folder for storing the override.
,
Apr 3 2018
Setting up overrides simply means selecting a local folder for storing them. Then chrome will ask for permission to store to the folder, answer in the affirmative. Once the override folder is set up, make a simple change, use ctrl-s to save the override. Set some breakpoints in the source tab. Reload the page.
,
Apr 3 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
,
Apr 3 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by vamshi.kommuri@chromium.org
, Apr 2 2018