Archaeology: Bug 1607316 | Other: Bug 1363508, Bug 1826051, Bug 1957658 This is not an area I am familiar with TBH, but I'll try my best. In Bug 1607316 (FF74) we spoofed the set of `pointer`, `any-pointer`, `hover`, `any-hover` differently to desktop. We've also had changes over time with, e.g. recently (Bug 1957658?) no longer bothering to try and hide touch on desktop (linux/mac) because it's impossible and also big deal (cuz we made all desktop look touch capable) - but I'm not sure if any of that code or what any previous code did re android. Which brings us to the current state of affairs. If you use https://arkenfox.github.io/TZP/tzp.html#css (the `CSS` section) and expand the `media` result you can see the four properties: two results each: one from css and one from matchmedia. Note each `any-pointer` test has two tests because the order matters - spec is at https://www.w3.org/TR/mediaqueries-4/#any-input > In the case of any-pointer, more than one of the values can match, if different pointing devices have different characteristics here are some android results (Samsung galaxy 2S4 FE) ``` chrome any-hover: hover hover: hover any-pointer: fine + coarse pointer: coarse FF (no RFP) any-hover: hover hover: none any-pointer: fine + coarse pointer: coarse FF+RFP and TB (all as designed, green ticks) any-hover: none hover: none any-pointer: coarse + coarse pointer: coarse ``` If the only thing we're trying to mask on android now is when a pen is _used_, then I don't understand why the above RFP is so adversarial (i.e not real world). IDK if these values can change based on connected devices (e.g. I have a samsung galaxy lastest model tablet with a keyboard/stand thing but haven't tested) so we obviously want to make sure out values are consistent - but AFAICT we don't need to enforce all hover as `none` and all pointer as `coarse` - to me that's a red flag that will one day be used against us I'll defer to pier since he's been doing a number of touch/pointer patches recently
Bug 2005506 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Archaeology: Bug 1607316 | Other: Bug 1363508, Bug 1826051, Bug 1957658 This is not an area I am familiar with TBH, but I'll try my best. In Bug 1607316 (FF74) we spoofed the set of `pointer`, `any-pointer`, `hover`, `any-hover` differently to desktop. We've also had changes over time with, e.g. recently (Bug 1957658?) no longer bothering to try and hide touch on desktop (linux/mac) because it's impossible and also big deal (cuz we made all desktop look touch capable) - but I'm not sure if any of that code or what any previous code did re android. Which brings us to the current state of affairs. If you use https://arkenfox.github.io/TZP/tzp.html#css (the `CSS` section) and expand the `media` result you can see the four properties: two results each: one from css and one from matchmedia. Note each `any-pointer` test has two tests because the order matters - spec is at https://www.w3.org/TR/mediaqueries-4/#any-input > In the case of any-pointer, more than one of the values can match, if different pointing devices have different characteristics here are some android results (Samsung galaxy 2S4 FE) ``` phone tablet [1] chrome tablet [2] any-hover: hover hover: hover any-pointer: fine + coarse pointer: coarse FF (no RFP) any-hover: hover hover hover: none none any-pointer: fine + coarse fine + coarse pointer: coarse coarse FF+RFP and TB (all as designed, green ticks) any-hover: none hover: none any-pointer: coarse + coarse pointer: coarse [1] Galaxy S11 Ultra with and without a cover-keyboard (does not have a touch pad) [2] paired with a Bluetooth mouse ``` If the only thing we're trying to mask on android now is when a pen is _used_, then I don't understand why the above RFP is so adversarial (i.e not real world). IDK if these values can change based on connected devices (e.g. I have a samsung galaxy lastest model tablet with a keyboard/stand thing but haven't tested) so we obviously want to make sure out values are consistent - but AFAICT we don't need to enforce all hover as `none` and all pointer as `coarse` - to me that's a red flag that will one day be used against us I'll defer to pier since he's been doing a number of touch/pointer patches recently