The SVGAElement interface in SVG 2.0 allows manipulation of <a> elements similar to HTML anchor elements. Supporting the rel and relList attributes enhances security and privacy for developers. This alignment with HTML anchor elements ensures consistency and ease of use across web technologies.
This is already supported in Firefox and Safari
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
The functionality of the rel and relList attributes is similar to how they operate for HTML <a> elements.
wpt.fyi links: https://wpt.fyi/results/svg/linking/scripted/a.rel-getter-01.svg https://wpt.fyi/results/svg/linking/scripted/rellist-feature-detection.svg Corresponding Chromium WPTs links: https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/web_tests/external/wpt/svg/linking/scripted/a.rel-getter-01.svg https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/web_tests/external/wpt/svg/linking/scripted/rellist-feature-detection.svg
Shipping on desktop | 135 |
Shipping on Android | 135 |
Shipping on iOS | 135 |
Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).
None--
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+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/27ceb04b-7b4e-4d64-99b5-13d4a621b002n%40chromium.org.
LGTM3