- From: hober <notifications@github.com>
- Date: Tue, 10 Sep 2019 19:21:13 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 11 September 2019 02:21:35 UTC
Hi, @dbaron and I have been looking at this during a breakout in Tokyo today. User agents have lots of information about the state of the device, and are able to intelligently pause or resume execution based on that information. Also, pausing and resuming execution is not "free", and may itself be a source of power etc. drain. The page author has significantly less information than the user agent, and the controls provided here are necessarily more coarse as a result. So I'm a bit worried that pages will engage in "cargo-cult" authoring behavior, and may complicate or interfere with the user agent's execution pausing logic. That said, if this usually results in significantly more execution pausing than the UA would have otherwise done, maybe it's a win. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/369#issuecomment-530191762
Received on Wednesday, 11 September 2019 02:21:35 UTC