-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add events for History API usage #402
Comments
@OrKoN can you share if |
In Puppeteer, we try to treat same-document navigations the same way as regular navigations. We use navigatedWithinDocument for this. For example, using the history API or navigating to |
@OrKoN, I assume that you accidentally pasted a different link here? This one goes to |
To clarify: the support for P.S. updated the link |
Isn't that |
I think it might be it: perhaps not implemented by the implementations yet? |
I think it is covered by this algorithm https://html.spec.whatwg.org/multipage/browsing-the-web.html#scroll-to-fragid (step 17.2)? |
Yes, it's not implemented in Firefox yet. I just filed https://bugzilla.mozilla.org/show_bug.cgi?id=1841039. @OrKoN does Chrome / CDP have it? Does it work as expected? If yes we potentially can close this issue. |
I think it is implemented in chromium-bidi. Perhaps we need to add some WPT tests? |
Yes, wdspec tests are missing for this event. Could someone from Google may implement those? I'm happy to review, and to include our implementation for the next milestone. |
let me take this (I will close the issue once the WPT test have landed) |
Which wpt tests do you reference here? Those for |
yes |
Ok, so the related PR has been merged. Does it mean we can now also close this issue or do you have to run more checks first? |
From my perspective, the current test set is sufficient (it only tests basic history API functions ) though but we already adjusted our implementation so it passes the tests. Unless someone sees a need for more History API tests, I would close now. |
We can / will certainly add more tests but this wouldn't require any new event for WebDriver BiDi. As such we can indeed close this issue. |
The BiDi events monitoring navigation and page load are not triggered when using the
history
API."history" navigations are quite different from real navigations, so it probably makes sense to avoid emitting the regular navigation events for those.
However it could be interesting to at least add a new event triggered when
popstate
is emitted by the History API. For instance, CDP offers thePage.navigatedWithinDocument
event which is emitted in this case.The
BrowsingContext
module could be a good fit for this new event.The text was updated successfully, but these errors were encountered: