Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign updevtools can't handle new pipelines #15425
Closed
Labels
Comments
|
cc @fitzgen |
bors-servo
added a commit
that referenced
this issue
Apr 28, 2020
Improve devtools experience when navigating The primary motivation for this work was to fix #15425, and these changes make it possible to use the devtools to meaningfully inspect multiple pages when navigating between them. Navigating through session history is not yet supported. These changes also include improvements to the dedicated worker support, which broke at some point. We now can observe console messages in workers.
bors-servo
added a commit
that referenced
this issue
Apr 28, 2020
Improve devtools experience when navigating The primary motivation for this work was to fix #15425, and these changes make it possible to use the devtools to meaningfully inspect multiple pages when navigating between them. Navigating through session history is not yet supported. These changes also include improvements to the dedicated worker support, which broke at some point. We now can observe console messages in workers.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Refreshes now give a different pipeline, and when you navigate to a new page, you also get a new pipeline. Devtools can currently only track a single pipeline (and it can't show historical data), so we can't effectively track network activity with it.
From discussion with @jdm:
We need some sort of coordination from the constellation (maybe?) to tell the devtools that pipeline 1 is navigating to pipeline 2 and the devtools should report stuff about pipeline 2 now