tools: Support tab navigation via navigateTo, goBack, and goForward#43026
Conversation
Signed-off-by: Brent Schroeter <[email protected]>
e4a1c2f to
5e5ddc5
Compare
Signed-off-by: Brent Schroeter <[email protected]>
5e5ddc5 to
251afcc
Compare
|
Requesting the appropriate testing label ( |
eerii
left a comment
There was a problem hiding this comment.
Tested it locally and it works pretty nice :) thanks!
For future reference (not this PR), remaining work in the navigation area that I can think of:
- Make the URL bar in DevTools update when navigating.
- Fix the inspector, as it breaks when navigating. I think one of the culprits here is that we are cloning the
pipeline_idandscript_senderfrom the browsing context actor to the inspector actor when we create it, but it is never updated. It would be better to pass the browsing context name and get the pipeline / sender from it, like you do here fortab.
Co-authored-by: eri <[email protected]> Signed-off-by: Brent Schroeter <[email protected]>
Thanks! I've been working on the other points you mention, and nearly have the inspector working across navigation, on a WIP branch. Updating the pipeline and sender correctly in |
|
That is great, thank you! Feel free to tag me in any other patch for a review :) |
…ervo#43026) Add support for navigation requests ("navigateTo", "goBack", and "goForward") over the Remote Debugging Protocol. These may be sent by a UI client in response to user input (for example the address bar in the Firefox inspector), or they can be used to automate navigation during unit tests. This currently only supports navigation within the URL domain at which servoshell is initially launched, due to a bug in servo's `BrowsingContextActor` implementation. (Unit tests covering a fix for that issue will depend on this change.) Testing: The behavior of all 3 new message types is covered by a new test case—`test_navigation`—in the devtools unit test suite. Fixes: servo#38668 --------- Signed-off-by: Brent Schroeter <[email protected]> Co-authored-by: eri <[email protected]> (cherry picked from commit 4c69d85)
Add support for navigation requests ("navigateTo", "goBack", and "goForward") over the Remote Debugging Protocol. These may be sent by a UI client in response to user input (for example the address bar in the Firefox inspector), or they can be used to automate navigation during unit tests.
This currently only supports navigation within the URL domain at which servoshell is initially launched, due to a bug in servo's
BrowsingContextActorimplementation. (Unit tests covering a fix for that issue will depend on this change.)Testing: The behavior of all 3 new message types is covered by a new test case—
test_navigation—in the devtools unit test suite.Fixes: #38668