[Bug]: Playwright's browsers dont behave as regular browsers
Version
1.46.1
Steps to reproduce
- Open https://mui.com/x/react-date-pickers/date-range-picker/ from your browser
- try to click check in input, then click MM, then DD, then YYYY and see that they properly get highlighted as shown in the video
https://github.com/user-attachments/assets/1ed1026a-43d2-4b22-b3d9-9e6847007af6
- Now open playwright browser, either chromium or firefox will do.
- Do the same action and see that none of them will get highlighted as shown in the video
https://github.com/user-attachments/assets/ceb122e6-4b1b-4c87-9718-0e7790533eba
Expected behavior
correctly be able to click the input fields on the browser as i can on my own browsers
Actual behavior
Although my tests pass locally, it kept failing on github actions. It'd mainly complain about firefox. It'd complain about not being able to input the dates at all (only firefox on github actions)
Additional context
No response
Environment
System:
Apple ARM Sonoma 14.4.1
Node 18.14.1
@playwright/test => 1.46.1
I’m also encountering issues with the DateRangePicker (v.7.11.0) when using Playwright version 1.46.1 and Firefox on my Docker server (image: mcr.microsoft.com/playwright:v1.46.1-noble). In addition to interaction problems, the screenshots are coming out incorrect and do not match the layout and behavior observed during manual testing in Firefox, that are correct.
It looks to me like you are in the Pick locator mode in your Playwright browser.
You should be able to toggle this to perform actions then enable it again if you need to select a locator. This might be a good feature request though. I do find it annoying to have to switch back and forth between selecting a locator and interacting with the page.
I am also facing this issue? Any work around for this?