Open
Bug 1005757
Opened 10 years ago
Updated 1 year ago
A way to pause the HTTP traffic after a certain resource in Network Monitor View.
Categories
(DevTools :: Netmonitor, enhancement, P3)
Tracking
(Not tracked)
NEW
People
(Reporter: karlcow, Unassigned)
References
(Blocks 1 open bug)
Details
This is slightly related to Bug 1005755. When debugging JS, there are ways to create breakpoints (with some conditions). It would be also very useful to be able to create a breakpoint in the HTTP timeline on certain resources. Basically, the first time the page is loaded in the network view, the developer can look at the HTTP resources. It would be good to be able to create a breakpoint and that all traffic stops before or after downloading this specific resources. That would make possible to understand some class of issues such as: * resources dependency * races conditions * rendering state in the timeline (and/or when a resource fails)
Comment 1•10 years ago
|
||
Somewhat related: bug 821610.
Comment 2•6 years ago
|
||
Karl will document when this happens again. - Should we pause before or after the resource? - Should we go offline or break in debugger?
Flags: needinfo?(kdubost)
Updated•6 years ago
|
Severity: normal → enhancement
Priority: -- → P3
Reporter | ||
Comment 3•6 years ago
|
||
Exhibit 1. In the issue https://webcompat.com/issues/16845 There is a JavaScript client side redirection based on User Agent detection. https://www.tealoungesystem.com/ redirects to https://www.tealoungesystem.com/errors/418.php saying that the browser is not supported. In order to analyze the Javascript, we need the window.relocation to not be effective and so the navigation context to not happen. In this case the pause should be before https://www.tealoungesystem.com/errors/418.php We still want to be able to analyze the JS code until the redirection.
Flags: needinfo?(kdubost)
Updated•6 years ago
|
Product: Firefox → DevTools
Updated•6 years ago
|
Blocks: devtools-webcompat-team
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•