Keyboard shortcut to open composer to reply to topic

I just tried on a different browser and at a different resolution (plugged into monitor) with no change. I tried on a second device, and then it shows up correctly.

image


The main difference here is of course that the image from my first computer includes “Mobile View” while the second includes “Keyboard Shortcuts”. Perhaps the conditions under which you include “Mobile View” will help indicate what’s going wrong here.

When plugged into the monitor, both computers used 1440p and 100% zoom, so there’s no logical reason they would render differently. When not plugged in, the first computer was at 1080p and 125% zoom. I guess it’s possible that something about my resolution settings was cached on Discourse even after refreshing the page, such that using the monitor didn’t change anything.

Regardless, it seems to me that some aspect of the “Mobile View” / “Keyboard Shortcuts” condition is using resolution rather than user agent, or something like that. Or maybe it’s that the zoom isn’t being properly accounted for. (It seems like screen.height and screen.width in JavaScript do account for zoom, but I obviously don’t know what you’re using for screen resolution detection, if you are at all).


It’s probably worth mentioning that I have previously run into issues with the view on my laptop doing mobile-like things on Discourse, presumably due to my resolution or zoom settings.

Slight tangent about laptop being treated as mobile device by Discourse

For example:
On laptop 1:
image

On laptop 2:
image

I don’t know if the facebook/twitter/email icons are desktop only, but I only see them in the one view. Or maybe (again) it’s just due to resolution.

There used to be a big difference in how the desktop and mobile views of the share buttons worked (prior to iOS Discourse going directly to the built in iOS share menu), and it was very noticeable that my laptop was using the mobile behavior by mistake.