FetchLater #2657
Comments
mingyc
added
the
feature definition
|
Thank you, we should indeed add this. The feature is shipping with Chrome and Edge 134. |
|
I saw and tested this but I haven't confirmed it shipping in Chrome 134 beta. |
|
We haven't enabled it for M134 Beta yet. |
|
Sorry maybe a noob question, but if we are already using Chromium WebFeature for FetchLater. Do we still need to switch to WebDXFeature, or can we log both? |
https://chromestatus.com/roadmap still has it as part of 134. Will it stay on 134, or likely move out to a later release?
Maybe @foolip will know how to reply to this, I'm not sure I understand what you mean by "Chromium WebFeature" vs. "WebDXFeature". I'm guessing this is about use-counters, but not sure. |
|
@mingyc assuming you're talking about use counters, you'd have to add a WebDXFeature use counter, even if you already added an old style WebFeature use counter already, but you can have both, no problem. Keep in mind, WebDXFeatures are different from old style use counters in that there is a 1:1 mapping between a use counter and a feature, they measure usage on a high level feature level, more about that in the public doc. |
|
@mingyc you must mean WebFeature::kFetchLater which is the classic use counter, the kind that we show data from on chromestatus.com. You can absolutely keep such use counters, and just add a simple mapping from them to "WebDXFeature" which is organized around web-features. https://chromium-review.googlesource.com/c/chromium/src/+/6269037 is an example of this I did recently. |
|
Update: The launch is delayed to M135. I've also sent out https://chromium-review.googlesource.com/c/chromium/src/+/6310147 as suggested above to map the classic use counter. |
- WebDX community [issue for FetchLater][1] - As suggested in [the discussion][2], this CL introduces a new WebDXFeature for FetchLaterAPI, and maps the existing use counter to it. [1]: web-platform-dx/web-features#2657 [2]: web-platform-dx/web-features#2657 (comment) Bug: 40276121 Change-Id: I539c038725254522d6553723a7780b1840b4bb74 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6310147 Commit-Queue: Ming-Ying Chung <[email protected]> Auto-Submit: Ming-Ying Chung <[email protected]> Reviewed-by: Tsuyoshi Horo <[email protected]> Cr-Commit-Position: refs/heads/main@{#1426974}
|
+1 from RUMvision (as we're writing a blogpost covering the deprecation of |
|
It is in Chromium 135. I collected compat data for it in mdn/browser-compat-data#26135 The keys are:
So, someone should create a web-feature with these BCD keys. |
|
I'll take this one. |
Specification
whatwg/fetch#1647
Description
Propose to add a new feature
FetchLaterfor the corresponding JS API.Documentation
https://github.com/WICG/pending-beacon/blob/main/docs/fetch-later-api.md
Browser support
The text was updated successfully, but these errors were encountered: