From 702dbc77ac11ac6094cf14ada70be7da13cea603 Mon Sep 17 00:00:00 2001 From: Andreu Botella Date: Tue, 23 Jul 2024 19:33:53 +0200 Subject: [PATCH] Add link to task attribution issue --- WEB-INTEGRATION.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/WEB-INTEGRATION.md b/WEB-INTEGRATION.md index 27eb41a..8813b9f 100644 --- a/WEB-INTEGRATION.md +++ b/WEB-INTEGRATION.md @@ -684,8 +684,8 @@ For snapshots exposed as properties of events, observer entries or other web platform objects, `CreateAsyncContextSnapshot()` should be called in the relevant realm of that web platform object. In any other cases (e.g. if a snapshot is passed as an argument into a callback), it should be called in the -relevant realm of `this` (see ). -It might therefpre make sense to instead define an equivalent of that abstract +relevant realm of `this` (see https://github.com/whatwg/webidl/issues/135). It +might therefore make sense to instead define an equivalent of that abstract operation in WebIDL, that handles this. Note that for properties of events and observer entries, implementations may @@ -710,8 +710,8 @@ as parameters. Some of these use cases are: useful [to identify scripts that enqueued long tasks](https://github.com/w3c/longtasks/issues/89), or to [build dependency trees for the loading of - resources](https://github.com/w3c/resource-timing/issues/263). See [TODO: open - issue in soft navigations spec] + resources](https://github.com/w3c/resource-timing/issues/263). See + https://github.com/WICG/soft-navigations/issues/44. - **`scheduler.yield` priority and signal**. In order to provide a more ergonomic API, if