Re: [w3ctag/design-reviews] Specification Review: FetchLater API (Issue #887)

Discussed during plenary this week. API seems fine, but the naming is a bit strange, "fetch later" could be misunderstood as a deferred fetch, when what you are getting is a guaranteed fetch when the document is gone. We don't have any better suggestions, but just wanted to point out the possibility of misunderstanding.

Explainer could use a bit more spelling out what the user story is. I have some speculations on how this could be used, but that's wildly speculative. Could you add some problems this proposal solves?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/887#issuecomment-1709579328
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/887/1709579328@github.com>

Received on Thursday, 7 September 2023 06:56:12 UTC