- From: Boris Zbarsky <web-platform-tests-notifications@w3.org>
- Date: Mon, 01 May 2017 16:47:02 GMT
- To: public-web-platform-tests-notifications@w3.org
There are outstanding issues on promises in navigated-away-from windows. The specs literal text currently requires that such promises continue running forever, even when the window has long since been navigated away from. This is a clear violation of user expectations and doesn't match what UAs do in practice in various situations, including Chrome. There are also outstanding issues on promises in windows whose browsing context has gone away, including whether those should behave similarly to promises in navigated-away-from windows or not. There's a bit less clarity around this in terms of user expectations and UA behavior, but once again UAs are not very consistent about it. As a simple example, in Chrome last I checked if you close a tab whether promises in it keep running depends on random things like whether other tabs are observing it, which process things got scheduled on, etc. But it's been a while since I checked; maybe that has been changed in the meantime. Per current (broken, imo) spec, of course, promise execution never stops, ever. There is simply no such concept in the spec. View on GitHub: https://github.com/w3c/web-platform-tests/pull/5738#issuecomment-298371327
Received on Monday, 1 May 2017 16:47:15 UTC