https://bugs.kde.org/show_bug.cgi?id=526812
--- Comment #4 from Nico <[email protected]> --- (In reply to David Redondo from comment #3) > That's wrong anyways, just because I have a touch device apps should not > display bigger controls, cf. laptops with touch displays. I meant that apps may keep controls large enough to use with a finger whenever touch input is available. That doesn't require assuming the user is currently using touch. Google's web.dev guide explicitly shows larger buttons when both a mouse and a touchscreen are available. MDN's any-pointer example does the same with checkboxes. Discourse also uses any-pointer: coarse to enable its touch styles on touchscreen laptops and desktops. On a touchscreen laptop, the user can switch between the mouse and the touchscreen, so that seems reasonable. Here, though, opening a keyboard-only session changes those capability checks on a laptop without a touchscreen. That can change unrelated interfaces even though the user's available input methods haven't changed. Is advertising touch capability necessary for a session that only has keyboard access? References: Google's web.dev example https://web.dev/learn/design/interaction#any_pointer MDN's checkbox example https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/At-rules/@media/any-pointer#examples Discourse's developer guide https://github.com/discourse/discourse/blob/a329d974d3a9446f472ec9617cf6e1d6ab8b9d92/docs/developer-guides/docs/03-code-internals/28-designing-for-devices.md#touch--hover -- You are receiving this mail because: You are watching all bug changes.
