-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Remove special handling for getSelection() with Firefox from tests #35271
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
base: main
Are you sure you want to change the base?
Conversation
It's Nightly only feature for now, I plan to give it some time before enabling it. So we should only remove the special-case handling after it's enabled in Release |
Oh, good point. Lets move this PR to draft for now. |
Enabling by default for all Firefox builds is covered by https://bugzilla.mozilla.org/show_bug.cgi?id=1954979. |
Test results for "tests 1"4 failed 4 flaky38780 passed, 808 skipped Merge workflow run. |
The fix will be in Firefox 139 - where it will be enabled by default. It will ride the trains and will be released on May 27th. If you want to get rid of this code already for 138 which is on beta now, you could temporarily use the But I think that this change can wait for the 139 release given that it was broken for such a long time. |
Ok, let's wait until it is released. |
I updated the PR to fix the actual merge conflicts in the tests. Do you already have an ETA for when your custom Firefox 139 will be available? |
Test results for "tests 1"7 failed 7 flaky39229 passed, 804 skipped Merge workflow run. |
We usually try to include current release of Firefox, so it we should roll 139 soon after it becomes stable. You can track our rolls in https://github.com/microsoft/playwright-browsers/blob/main/browser_patches/firefox/BUILD_NUMBER |
We got https://bugzilla.mozilla.org/show_bug.cgi?id=85686 in Firefox fixed for version 138 which is currently in Nightly. That means that we no longer need to special-case the handling for
getSelection()
with Firefox.I assume this PR needs to wait with getting merged until Firefox 138 is going to be released?