-
Notifications
You must be signed in to change notification settings - Fork 1.1k
chore: roll to 1.57.0-beta-1763718928000 #3007
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
Conversation
| ) -> None: | ||
| await self._click(**locals_to_params(locals())) | ||
|
|
||
| async def _click( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is unfortunate!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
true that! but without this separation, we'd have a frame.click(steps=) param
| def ensure_trailing_slash(url: str) -> str: | ||
| split = url.split("://", maxsplit=1) | ||
| if len(split) == 2: | ||
| # URL parser doesn't like strange/unknown schemes, so we replace it for parsing, then put it back |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was this comment incorrect? Could it be python-version-specific?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure if it was incorrect. Certainly not version specific, urlparse didn't change much in the past years: https://github.com/python/cpython/blob/3.14/Lib/urllib/parse.py
The implementation definitely wasn't correct for the my.custom.protocol test cases. And I figured that instead of trying to understand its behaviour, I just implement the WHATWG spec.
Closes #2985