You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The spec tests a bunch of different sites first evaling the media query, goto page, and evaluate the media query again. On most sites (pointer: fine) evaluates as true in both checks, however there are a few that don't.
Expected behavior
In headless chromium with given run settings the media query (pointer: fine) will be consistent regardless of the current web page.
Actual behavior
Some web pages change the value of the media query (pointer: fine) to false.
Additional context
Might be a bug in headless Chromium, it works in headed mode for both docker and native.
The text was updated successfully, but these errors were encountered:
kevswanberg
changed the title
[Bug]: Headless chromium media query (pointer: fine) changing on some web pages while running in docker
[Bug]: Headless chromium media query (pointer: fine) changing on some web pages while running in docker image and native linux
Nov 23, 2024
Version
1.49.0
Steps to reproduce
In the playwright docker image container and on native linux Chromium, the media query for pointer type will change after going to certain pages.
Here is a test project going to several different pages, running the same media query before and after. Certain pages consistently fail.
The spec tests a bunch of different sites first evaling the media query, goto page, and evaluate the media query again. On most sites
(pointer: fine)
evaluates as true in both checks, however there are a few that don't.Expected behavior
In headless chromium with given run settings the media query
(pointer: fine)
will be consistent regardless of the current web page.Actual behavior
Some web pages change the value of the media query
(pointer: fine)
to false.Additional context
Might be a bug in headless Chromium, it works in headed mode for both docker and native.
Possibly related:
#18777
This mentions headed but it currently it seems like the issue is fixed in headed mode.
https://issues.chromium.org/issues/40903645?pli=1
Environment
The text was updated successfully, but these errors were encountered: