Re: [w3ctag/design-reviews] Incubation: CPU Performance API (Issue #1198)

RByers left a comment (w3ctag/design-reviews#1198)

> The case that proponents seem to be glossing over is what happens in the mis/abuse cases.

Can you clarify what sort of misuse / abuse you anticipate? I don't see abuse discussed above at all really. Or do you just mean fingerprinting? 

One potential misuse I was concerned with was where a site uses this feature to degrade functionality unnecessarily, or to make a tradeoff that may or may not be aligned with the user's interests without giving them input (eg. decreasing resolution to reduce the risk of dropped frames). Of course that's a general concern with app design which browsers can't solve completely, but I do agree that [The web can be consumed in any way that people choose](https://w3ctag.github.io/ethical-web-principles/#render). To me that's a reason to prefer having such an API vs. leaving sites to make such tradeoffs themselves without assistance from browser APIs. I think the spec is silent on this point, but In Chrome we've implemented this with the following settings UI:

<img width="695" height="143" alt="Image" src="https://github.com/user-attachments/assets/a5f1dcf6-1ef9-4817-8d9b-e2bf60db0207" />

If this UI gets used much at all in practice, then I could imagine investing more to make it a site-specific setting if users say they'd prefer that. Perhaps the spec should comment on this?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1198#issuecomment-4769064527
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1198/4769064527@github.com>