LordAverie 0 Posted November 16, 2023 Posted November 16, 2023 For over a month, my emby web app has been stuck in Tablet/Mobile Display Mode, changing the setting does nothing. I use Firefox, the problem persists even on a clean firefox install, but the problem does not happen on Microsoft Edge on the same device. On my laptop, also running Firefox, the Display Mode is set to Desktop, but can't be changed either (maybe it's just automatic or server-side?). According to my browser the User-Agent is reported correctly as Firefox/Windows, there aren't any cookies on the site so I can't try editing those either. Overall I have no idea what it could be any more.
Luke 42077 Posted November 16, 2023 Posted November 16, 2023 Hi, is Firefox up to date? Do you have any touch input devices connected?
LordAverie 0 Posted November 16, 2023 Author Posted November 16, 2023 2 minutes ago, Luke said: Hi, is Firefox up to date? Do you have any touch input devices connected? Yes, it is always up to date, this issue has persisted for at least one update. I have no touch devices plugged in, but I do have drivers for a drawing tablet installed.
Luke 42077 Posted November 16, 2023 Posted November 16, 2023 So Firefox is telling us that touch is your primary input method. Does it have any options to control this?
LordAverie 0 Posted November 17, 2023 Author Posted November 17, 2023 I have disabled touch support through the config, cleared site data, then logged in again. My issue persists
LordAverie 0 Posted November 18, 2023 Author Posted November 18, 2023 apz.drag.touch.enabled | browser.touchmode.auto | dom.w3c_touch_events.enabled I set the first two to false, and the last to 0 (disabled), it was 2 (auto-detect) before
Luke 42077 Posted November 18, 2023 Posted November 18, 2023 Can you open this page and take a screenshot of the top section called your device: https://hoverpointer-media-query.glitch.me/ What you should be seeing there is the hover:hover section as well as the pointer: fine section in green, and the others all in red.
LordAverie 0 Posted November 18, 2023 Author Posted November 18, 2023 I feel like this issue could be easily remidied by making the display mode option in the settings actually change the display mode.
Luke 42077 Posted November 19, 2023 Posted November 19, 2023 What version of Firefox? https://bugzilla.mozilla.org/show_bug.cgi?id=1638556
LordAverie 0 Posted November 25, 2023 Author Posted November 25, 2023 I had drivers for a digitised pen installed, which firefox recognises, this has never been an issue in years on any website, except this one. I had to disable the driver entirely to get desktop mode to show up. Why doesn't this website use the user-agent for this? Why doesn't the setting to change display mode work?
Luke 42077 Posted November 25, 2023 Posted November 25, 2023 6 hours ago, LordAverie said: I had drivers for a digitised pen installed, which firefox recognises, this has never been an issue in years on any website, except this one. I had to disable the driver entirely to get desktop mode to show up. Why doesn't this website use the user-agent for this? Why doesn't the setting to change display mode work? The user agent can't tell us what we need to know. We need to know your primary input method, and css media queries can tell us that. It allows the web app to work well across a variety of use cases, screens, input methods, etc. But everything comes with a cost, and so for this unfortunately we do have to deal with the occasional case of the browser reporting it incorrectly, so that's why this happened. Why doesn't the display mode setting work - because the switching between mobile and desktop has been automatic for the last few years, handled by the css media queries I mentioned above. That means the two options are actually the same thing, but they are still kept around in case we may have a use for them in the future.
TeamB 2438 Posted November 25, 2023 Posted November 25, 2023 I am seeing https://patrickhlauke.github.io/touch/pointer-hover-any-pointer-any-hover/ is showing the same hover: hover = false pointer: fine = false So its a firefox thing, just need to work out why. 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now