LGTM2, predicated of course on completing the privacy, security, and debuggability sections within the tool.
Best, Alex On Monday, September 8, 2025 at 7:23:11 PM UTC+1 dan...@microsoft.com wrote: > LGTM1 > > On Thursday, September 4, 2025 at 1:04:17 AM UTC-7 Chromestatus wrote: > >> Contact emails rags...@microsoft.com >> > >> Explainer None >> >> Specification >> https://svgwg.org/svg2-draft/linking.html#InterfaceSVGAElement >> >> Summary >> >> This feature introduces support for the download attribute on the >> SVGAElement interface in Chromium, aligning with the SVG 2 specification. >> The download attribute enables authors to specify that the target of an SVG >> hyperlink should be downloaded rather than navigated to, mirroring the >> behavior already supported in HTMLAnchorElement. This enhancement promotes >> interoperability across major browsers and ensures consistent behavior >> between HTML and SVG link elements, thereby improving developer experience >> and user expectations. >> >> >> Blink component Blink>SVG >> <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3ESVG%22> >> >> TAG review None >> >> TAG review status Not applicable >> >> Risks >> >> >> Interoperability and Compatibility >> >> Interoperability Risk: Low The download attribute on SVGAElement is >> currently supported in Firefox, with no known support in Safari/WebKit or >> other engines. The implementation is based on a well-defined behavior >> already supported in HTMLAnchorElement and formalized in the SVG 2 >> specification. Compatibility Risk: Very Low SVG links without the download >> attribute will continue to behave as they do today. For content that does >> use the attribute, the behavior will mirror that of HTML anchor elements, >> minimizing surprises and reducing the learning curve for developers. >> Overall, this change is expected to improve interoperability and developer >> experience with minimal risk to compatibility or stability. >> >> >> *Gecko*: Shipped/Shipping ( >> https://developer.mozilla.org/en-US/docs/Web/SVG/Reference/Element/a#browser_compatibility) >> >> >> >> *WebKit*: Positive ( >> https://github.com/WebKit/standards-positions/issues/543) >> >> *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? >> >> None >> >> >> Debuggability >> >> The implementation of the download attribute on SVGAElement builds upon >> Chromium’s existing anchor element infrastructure, ensuring consistent >> behavior and straightforward debugging. Developers can inspect and interact >> with the attribute using standard DevTools workflows. >> >> >> 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 >> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> >> ? No >> >> While Web Platform Tests (WPT) are not suitable for validating actual >> file downloads—due to the limitations of sandboxed test environments and >> the inability to reliably assert file system interactions—we have instead >> added browser tests to verify the functionality. These browser-level tests >> simulate user interactions and confirm that the download behavior is >> correctly triggered and handled by the browser. This approach ensures >> accurate validation of the feature in a controlled environment, where >> download flows can be observed and asserted reliably. >> >> >> Flag name on about://flags >> >> Finch feature name SvgAnchorElementDownloadAttribute >> >> Rollout plan Will ship enabled for all users >> >> Requires code in //chrome? False >> >> Tracking bug https://issues.chromium.org/issues/40589293 >> >> Estimated milestones >> Shipping on desktop 142 >> Shipping on Android 142 >> Shipping on WebView 142 >> Shipping on iOS 142 >> >> Anticipated spec changes >> >> 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 >> >> Link to entry on the Chrome Platform Status >> https://chromestatus.com/feature/6265596395913216?gate=6210629270241280 >> >> This intent message was generated by Chrome Platform Status >> <https://chromestatus.com>. >> > -- 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/bf908bda-4028-4a62-8ea0-8b792c218c4bn%40chromium.org.
