- From: bvandersloot-mozilla via GitHub <sysbot+gh@w3.org>
- Date: Tue, 11 Feb 2025 19:13:14 +0000
- To: public-device-apis-log@w3.org
bvandersloot-mozilla has just created a new issue for https://github.com/w3c/compute-pressure: == Consider less implementation-defined definitions for PressureState == Hello, coming over from [Mozilla's standards-position thread](https://github.com/mozilla/standards-positions/issues/521#issuecomment-2590757814) on this spec. I have feedback around one concern. The map from contributing factors (and those contributing factors themselves) to PressureStates are left very implementation-defined. This introduces risk that an application that relies on this would behave very differently between browsers. Consider a webapp developed against the heuristics employed by one browser, running on a browser that provides less aggressive signalling of pressure. The webapp may not take the warnings on the second browser for the dire warning the are and keep pushing for a bit. This would lead to some hard-to-diagnose and vague webcompat bugs of intermittent reduced quality under some conditions for one browser for that app. I'm not familiar with the OS signals exposed, or how each OS decides when to throttle processes, so I don't have too much to go on here. However, did consideration go into specifying the production of the PressureStates any more closely? Please view or discuss this issue at https://github.com/w3c/compute-pressure/issues/307 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 11 February 2025 19:13:15 UTC