Summary: | Web Inspector: "Deactivate/Activate All Breakpoints" should be disabled when there are no breakpoints | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | sam <dsam2912> | ||||
Component: | Web Inspector (Deprecated) | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | RESOLVED WONTFIX | ||||||
Severity: | Normal | CC: | apavlov, burg, bweinstein, joepeck, keishi, loislo, pfeldman, pmuellr, rik, vivekgalatage, yurys | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Attachments: |
|
Breakpoints can be dynamically added as scripts are parsed and removed as pages are reloaded. Blocking activate / deactivate during these transitions does not make UI more intuitive. I would be oppose to such change. (In reply to comment #1) > Breakpoints can be dynamically added as scripts are parsed and removed as pages are reloaded. Blocking activate / deactivate during these transitions does not make UI more intuitive. I would be oppose to such change. Thanks for your feedback Pavel, I think its a bit of confusing to keep activate / deactivate enabled when there are no breakpoints. Also when breakpoints are getting updated dynamically as you pointed out, the button would become disabled iff there are no breakpoints. I am not very sure of occurrences of the cases where we have breakpoints/no-breakpoints in quick successions. Plz let me know your thoughts. |
Created attachment 143784 [details] Illustration for problem description. "Deactivate/Activate All Breakpoints" button on Source panel should be disbaled when there are no breakpoints.