Skip to content
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

RFC 74: Add testdriver.js support for WebDriver delete_all_cookies command #74

Merged
merged 2 commits into from
Dec 9, 2020

Conversation

miketaylr
Copy link
Member

PR to add support for delete_all_cookies here: web-platform-tests/wpt#26723

@annevk
Copy link
Member

annevk commented Dec 3, 2020

WebDriver doesn't seem particularly detailed about how it serializes cookie values. That seems rather important to address first, at least before adding anything apart from "delete all", given that JSON doesn't have a native representation for byte sequences. (This concern might also apply to cookie names, not sure.)

@miketaylr
Copy link
Member Author

at least before adding anything apart from "delete all"

This is the one bit I'm actually interested in right now, so I'm happy to reduce the scope of the RFC to land this without blocking on the rest.

@annevk
Copy link
Member

annevk commented Dec 3, 2020

Sounds good, I filed w3c/webdriver#1562 on WebDriver for the serialization issue.

@jgraham
Copy link
Contributor

jgraham commented Dec 3, 2020

I think this makes sense.

@miketaylr miketaylr changed the title RFC 74: Add testdriver.js support for WebDriver cookie commands RFC 74: Add testdriver.js support for WebDriver delete_all_cookies command Dec 3, 2020
@miketaylr
Copy link
Member Author

Sounds good, I filed w3c/webdriver#1562 on WebDriver for the serialization issue.

Thanks. I've updated the RFC as well.

Copy link
Contributor

@stephenmcgruer stephenmcgruer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.


## Risks

This increases the API surface of testdriver.js, so it's more code to maintain or reason about. In addition, the developer experience of running local cookie tests will be less convenient (requiring `wpt run` instead of just hitting refresh).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As just a side-note; if you running a single test under wpt run we do keep the test window open after the test finishes and I believe refreshing the test should work fine. (Unless there's weird stateful things happening I don't know about).

@miketaylr
Copy link
Member Author

It's been 7 days with no objections, shall we merge this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants