Caută ajutor

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Acest fir de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

Prevent Buggy Automatic Unwanted Javascript Debugging When Page Is Refreshed While Inspecting

  • Niciun răspuns
  • 1 are această problemă
  • 1 vizualizare
more options

Firefox Developer Edition v59 on Windows 10

Inspect Elements opens the DOM and Inspector tab allowing developers to identify a classname for example, go into our IDE, add or edit the CSS properties and refresh the page for review.

Yes, I know we can change CSS in the Developer Tools but that is not efficient nor practical when inspecting and modifying multiple CSS properties for an area in a page when multiple changes that need to be saved and reviewed to determine if the CSS edits made in the IDE are appropriate and work well with the rest of the content in the page that is displayed.

As soon as the page is refreshed while the Inspector tab is opened the Javascript Debugging starts and switches to the Javascript Debugger tab and begins debugging the Javascript in the page. THIS IS A BUG that has been BUGGING ME FOR AT LEAST A YEAR.

How do we stop the debugger from running on a page refresh when all we want to do is Inspect, modify, refresh and continue Inspecting if wanted? Well designed and tested software does not decide to start and run code on its own and that's what the Developer Tools do when the page is refreshed when Inspecting the DOM.

I might add Chrome does not have this bug. When will this bug be resolved or how is it to be worked-around as it is not only annoying it is costly in time to respond to and breaks a developer's concentration to respond to the bug because the developer is compelled to go back and forth to stop unwanted behavior of this browser and restart the intended functionality.

Firefox Developer Edition v59 on Windows 10 Inspect Elements opens the DOM and Inspector tab allowing developers to identify a classname for example, go into our IDE, add or edit the CSS properties and refresh the page for review. Yes, I know we can change CSS in the Developer Tools but that is not efficient nor practical when inspecting and modifying multiple CSS properties for an area in a page when multiple changes that need to be saved and reviewed to determine if the CSS edits made in the IDE are appropriate and work well with the rest of the content in the page that is displayed. As soon as the page is refreshed while the Inspector tab is opened the Javascript Debugging starts and switches to the Javascript Debugger tab and begins debugging the Javascript in the page. THIS IS A BUG that has been BUGGING ME FOR AT LEAST A YEAR. How do we stop the debugger from running on a page refresh when all we want to do is Inspect, modify, refresh and continue Inspecting if wanted? Well designed and tested software does not decide to start and run code on its own and that's what the Developer Tools do when the page is refreshed when Inspecting the DOM. I might add Chrome does not have this bug. When will this bug be resolved or how is it to be worked-around as it is not only annoying it is costly in time to respond to and breaks a developer's concentration to respond to the bug because the developer is compelled to go back and forth to stop unwanted behavior of this browser and restart the intended functionality.