Open
Bug 1505965
Opened 7 years ago
Updated 3 years ago
Allow to create XHR breakpoints for XHR's URLs
Categories
(DevTools :: Netmonitor, enhancement, P3)
DevTools
Netmonitor
Tracking
(Not tracked)
NEW
People
(Reporter: Harald, Unassigned)
Details
User Story
When debugging an XHR issue in the Network panel, I want to be able to quickly set a breakpoint for specific resource, so that I can pause on the right line without having to manually enter the URL in the debugger. When adding a breakpoint on a resource, I want the UI to switch to the Debugger, so that I can see the breakpoint being added as confirmation.
Attachments
(1 file)
|
12.22 KB,
image/png
|
Details |
image.png
No description provided.
|
Reporter | |
Updated•7 years ago
|
Summary: Expose "Break on this XHR" menu item for XHR resources → Allow to create XHR breakpoints for XHR's URLs
|
||
Comment 1•7 years ago
|
||
Thanks for the report, I like that idea.
Some comments/inspiration:
1) There could be a new context menu action "Create Breakpoint". So, the user can right-click on a request, pick the menu action and be navigated to the Debugger panel
2) The Network panel could indicate whether there is a breakpoint created for existing XHR. E.g. Firebug had a breakpoint column on the left side (similarly to what the Debugger panel has for source). This column was also used to create/remove it (see the attached image).
Honza
|
|
||
Updated•7 years ago
|
Priority: -- → P3
|
|
Reporter | |
Comment 2•7 years ago
|
||
Taking an MVP approach, 1) would be the easiest; so Network panel does not need to know about XHR Breakpoints. Right-click menus are proliferating a bit too much, and I would hypothesize that we would not win a lot of new debugger users through this.
As reference for 2): http://www.softwareishard.com/blog/firebug/firebug-15-xhr-breakpoints/
Optimizing for discovery, this is best and would really provide an intuitive way to pause and navigate XHRs.
|
||
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•