We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This is to track step 2 of #19, which appears to be the only remaining step.
These endpoints can be define in the Page Lifecycle spec directly, with https://w3c.github.io/permissions/#automation being an example of how that's done.
The endpoints in ChromeDriver are:
POST /session/{session id}/goog/page/freeze
POST /session/{session id}/goog/page/resume
The remote end steps should probably use one of the algorithms in https://wicg.github.io/page-lifecycle/#changing-frozenness.
The text was updated successfully, but these errors were encountered:
cc @Hexcles, since we chatted about this earlier
Sorry, something went wrong.
No branches or pull requests
This is to track step 2 of #19, which appears to be the only remaining step.
These endpoints can be define in the Page Lifecycle spec directly, with https://w3c.github.io/permissions/#automation being an example of how that's done.
The endpoints in ChromeDriver are:
POST /session/{session id}/goog/page/freeze
POST /session/{session id}/goog/page/resume
The remote end steps should probably use one of the algorithms in https://wicg.github.io/page-lifecycle/#changing-frozenness.
The text was updated successfully, but these errors were encountered: