Contact emails apaselti...@chromium.org
Explainer https://github.com/WICG/attribution-reporting-api/blob/main/EVENT.md#registering-attribution-sources Specification https://wicg.github.io/attribution-reporting-api/#html-monkeypatches Summary For Attribution Reporting, the attributionsrc attribute was already unintentionally processed on <area> elements due to code shared with <a>, which intentionally supported that attribute. For completeness, we expose the attribute on <area> with identical syntax and semantics to <a> and without changing the previous processing: When an <area> tag with an attributionsrc attribute is navigated, the foreground request may register navigation sources and, if the attribute is non-empty, one or more background requests will likewise be able to register navigation sources. Blink component Blink TAG review Covered by existing Attribution Reporting I2S as this is a small change re-using the existing API surface. TAG review status Not applicable Risks Interoperability and Compatibility None Gecko: No signal WebKit: No signal Web developers: No signals Other signals: WebView application risks Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications? No. Debuggability None Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)? Yes Is this feature fully tested by web-platform-tests? Yes Flag name on about://flags None Finch feature name None Non-finch justification This is a minor change largely reusing existing code and behavior. The only web-exposed detail here is the addition of an already-processed HTML attribute to the corresponding tag's IDL definition. Requires code in //chrome? False Tracking bug https://issues.chromium.org/379275911 Measurement n/a Availability expectation Covered by existing Attribution Reporting I2S as this is a small change re-using the existing API surface Adoption expectation Covered by existing Attribution Reporting I2S as this is a small change re-using the existing API surface Adoption plan n/a Non-OSS dependencies Does the feature depend on any code or APIs outside the Chromium open source repository and its open-source dependencies to function? No. Estimated milestones Shipping on desktop 133 Shipping on Android 133 Shipping on WebView 133 Anticipated spec changes Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (eg links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (eg, changing to naming or structure of the API in a non-backward-compatible way). n/a Link to entry on the Chrome Platform Status https://chromestatus.com/feature/6547509428879360?gate=6545976813420544 This intent message was generated by Chrome Platform Status. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/673f72a6.2b0a0220.3bb1d2.02f2.GAE%40google.com.
