Bugzilla

(In reply to Tom Ritter [:tjr] from comment #0)
> `CSSPointerCapabilities` hardcodes the pointer / any-pointer / hover / any-hover behavior to the platform defaults (Fine|Hover on Desktop, and Coarse on Android)

I don't think this is true for desktop, it's been a few years and maybe something has changed that I missed - would be nice to clarify exactly what is protected for RFP and TZP health checks, so pinging pierov: AFAIK (this is what TZp checks for)
- desktop:
  - `any-pointer`: only allows the capability `fine` i.e we should be `fine + fine`
  - `pointer`: we don't protect because we thought everyone would be `fine`
      - but sounds like we should? see 0.5% windows users who have a primary pointer of none or coarse
  -  `hover` and `any-hover`: we don't protect because everyone should be hover already?

android: RFP/TZP health _should_ currently be as follows (pending bug 2005506)
  - `any-pointer`: only allows the capability `coarse` i.e we should be `coarse + coarse`
  - `pointer`: `coarse`
  - `hover, `any-hover`: `none`

note: the origins of my knowledge on what is and what isn't is lost in the fog of time and bugzillas

pierov, can you confirm what the desktop protections currently are, thanks

(In reply to Tom Ritter [:tjr] from comment #0)
> `CSSPointerCapabilities` hardcodes the pointer / any-pointer / hover / any-hover behavior to the platform defaults (Fine|Hover on Desktop, and Coarse on Android)

I don't think this is true for desktop, it's been a few years and maybe something has changed that I missed - would be nice to clarify exactly what is protected for RFP and TZP health checks, so pinging pierov: AFAIK (this is what TZp checks for)
- desktop:
  - `any-pointer`: only allows the capability `fine` i.e we should be `fine + fine`
  - `pointer`: we don't protect because we thought everyone would be `fine`
      - but sounds like we should? see 0.5% windows users who have a primary pointer of none or coarse
  -  `hover` and `any-hover`: we don't protect because everyone should be hover already?

android: RFP/TZP health _should_ currently be as follows (pending bug 2005506)
  - `any-pointer`: only allows the capability `coarse` i.e we should be `coarse + coarse`
  - `pointer`: `coarse`
  - `hover`, `any-hover`: `none`

note: the origins of my knowledge on what is and what isn't is lost in the fog of time and bugzillas

pierov, can you confirm what the desktop protections currently are, thanks