- From: Marcos Caceres <marcos@marcosc.com>
- Date: Thu, 16 Sep 2021 13:37:03 +1000
- To: public-webapps <public-webapps@w3.org>
Hi WebApps WG members (Editors in particular!), I wanted to bring your attention to some fantastic guidance that was recently added to the TAG's Design Guidelines around non-"fully active" documents (formal definition at [1]): that is, documents that lack a browsing context, which can happen in certain scenarios - like when an iframe is removed but there still being a javascript reference to it so it can't be garbage collected, or a document is in the "back/forward cache". This can be a source of undefined behavior, or worse, it can cause inconsistent behavior such as events not being delivered or promises not being resolved/rejected, causing web applications to unexpectedly stall/break. If you are editing a spec, or are a bit of a browser-edge-case enthusiast 🤓, I suggest reading the following great new guidance that was prepared by Rakina Zata Amni (Google) and other clever folks: https://w3ctag.github.io/design-principles/#support-non-fully-active If you have any questions, or want me to check if this affects your spec, give me a shout! Kind regards, Marcos [1] https://html.spec.whatwg.org/#fully-active
Received on Thursday, 16 September 2021 03:38:19 UTC