- From: Divyansh Mangal via GitHub <noreply@w3.org>
- Date: Mon, 10 Nov 2025 07:33:48 +0000
- To: public-svg-issues@w3.org
goldenboy777 has just created a new issue for https://github.com/w3c/svgwg: == Specifying processing model and algorithm for `ping` and `referrerPolicy` in SVG `a` element == Chromium is planning to support the hrefLang, type, ping, and referrerPolicy attributes for SVGAElement ([Intent to Ship](https://chromestatus.com/feature/5140707648077824?gate=6224522713890816)), in alignment with the [SVG2 specification](https://svgwg.org/svg2-draft/linking.html#InterfaceSVGAElement). Following the links related to referrerPolicy in the spec ([reference](https://svgwg.org/svg2-draft/linking.html#AElementReferrerpolicyAttribute)), it states: >These attributes further describe the targetted resource and its relationship to the current document. Allowed values and meaning are [as defined for the a element in HTML](https://html.spec.whatwg.org/multipage/text-level-semantics.html#the-a-element). While the expected behaviour of these attributes should mirror that of HTML `a` elements, there is ambiguity regarding the processing model and algorithms, particularly for `ping` and `referrerPolicy`. This concern has been raised by Chromium API owners and echoed by WebKit contributors ([signal discussion](https://github.com/WebKit/standards-positions/issues/566)). Should the SVG2.0, be updated to include this information explicitly? Should relevant links corresponding to processing model and algorithm of HTMLAnchorElement be given for that? Please view or discuss this issue at https://github.com/w3c/svgwg/issues/1029 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 10 November 2025 07:33:49 UTC