Minutes, 8 January 2026 SVG WG telcon

Minutes from today’s telcon are below.

 https://www.w3.org/2026/01/08-svg-minutes.html



Kind regards,
Dirk

IRC log of svg on 2026-01-08

Timestamps are in UTC.

06:36:22 [RRSAgent]
RRSAgent has joined #svg
06:36:27 [RRSAgent]
logging to https://www.w3.org/2026/01/08-svg-irc

06:39:35 [ydaniv]
ydaniv has joined #svg
06:43:21 [viralipurbey]
viralipurbey has joined #svg
06:46:29 [Vinay]
Vinay has joined #svg
06:46:35 [Vinay]
present+
06:46:54 [caribou]
present+
06:47:08 [krit]
present+
06:47:15 [viralipurbey]
present+
06:47:26 [krit]
scribenick: krit
06:47:48 [krit]
topic: naturalWidth and naturalHeight in the context of an HTML image
06:48:00 [ydaniv]
present+
06:48:01 [karlcow]
https://github.com/w3c/svgwg/issues/1044

06:48:01 [krit]
https://github.com/w3c/svgwg/issues/1044

06:48:09 [dmangal]
dmangal has joined #svg
06:48:51 [krit]
karlcow: SVG is used as an image in the src attribuite as an image.
06:49:14 [dmangal]
present+
06:49:34 [krit]
karlcow: UA would fetch width and height from SVG if present. No issue then. But what happens when one of both or none is present.
06:50:19 [krit]
karlcow: There is a different behavior across UIs for naturalWidth and naturalHeight. We are fixing issues on our side.
06:50:43 [krit]
karlcow: What should be returned for document.querySelector('img').naturalWidth document.querySelector('img').naturalHeight
06:51:07 [krit]
karlcow: SVG spec says auto which is 100%. But doesn't say anything about what happens if the attribute is not present.
06:51:24 [krit]
karlcow: should auto be 100%? What is 100%?
06:52:04 [krit]
krit: Doesn't CSS sizing spec define something as a default?
06:52:14 [krit]
karlcow: There is withh 400x150
06:53:14 [krit]
karlcow: There might be web compat issues. E.g if you have a super large with and maintain aspect ratio. It would create an image that does not fit the page... something very bug
06:53:20 [krit]
s/bug/big/
06:53:59 [krit]
s/400x150/300x150/
06:54:41 [krit]
karlcow: In Chrome and Gecko, there is a limit up to which dimension can get displayed.
06:55:57 [krit]
karlcow: If naturalWidth/naturalHeight is not available, there is a fallback defined. We should add a reference to the HTML spec in SVG spec what happens of an SVG image (with missing width/height) UA should follow the HTML spec.
06:56:39 [krit]
krit: We would require a normative reference to the HTML spec. Unsure if we should do that. Can we define the same text in SVG?
06:56:46 [krit]
karlcow: we could do, yes.
06:57:20 [krit]
caribou: I am not sure if that is an issue that needs to get defined/fixed in the SVG spec.
06:57:35 [krit]
caribou: though it does seem to be an compat issue.
06:57:56 [krit]
karlcow: What is the concern with a normative reference to the HTML spec?
06:58:17 [Neha]
Neha has joined #svg
06:58:23 [Neha]
present+
06:58:39 [Neha]
q+
07:00:12 [dmangal]
dmangal has joined #svg
07:00:34 [Neha]
ack me
07:02:58 [krit]
krit: IMO it should be part of the HTML spec to define what naturalWidth/naturalHeight even means for vector formats. But the SVG spec should define what it means in this context or at least provide context to the HTML spec.
07:03:07 [krit]
caribou: we could define the aspect ratio
07:03:34 [krit]
krit: aspect ratio is defined as part of the viewBox attribute.
07:04:12 [krit]
caribou: it seems fine to let HTML spec define it
07:06:02 [krit]
krit: If there is anything missing in specific context in the SVG spec, I am fine with being more specific in the SVG spec. At this point I am not sure if there is anything missing though.
07:06:14 [krit]
caribou: lets keep the issue open and bring it back to the WAHTWG
07:06:58 [krit]
action: Karl will get back to WHATWG to ask if there is something missing with regards to naturalWidth/naturalHeight in the SVG spec
07:07:18 [krit]
topic: Bikeshed migration
07:07:45 [krit]
karlcow: I continued to work on the conversion of the spec to Bikeshed and made good progress.
07:07:53 [krit]
karlcow: 1/3 has been migrated
07:08:07 [krit]
karlcow: Links to chapters are working already.
07:08:57 [krit]
karlcow: There are still a few breakages with regards to markup but not much of a challenge
07:09:43 [krit]
karlcow: My concern, is the XML file containing all SVG element definitions
07:10:11 [krit]
karlcow: Bikeshed will get to the XML file, fetches the information and adds that to the Bikeshed content.
07:10:58 [krit]
karlcow: I wonder if we want to do the conversion once: Migrate the XML to actual Bikeshed or if we want to add a pre-processing spec to read the information from XML.
07:11:46 [krit]
karlcow: I suppose the previous bheavior with the XML document made sense. But on going, we might not want to keep it.
07:12:41 [krit]
krit: I believe there were a use case to read and verify information beyond the spec but don't know what it was.
07:13:32 [krit]
krit: Is there a way to extract element and attribute definitions from the Bikeshed document?
07:13:54 [krit]
caribou: if yes, we could, if required, extract the information back from the Bikeshed spec.
07:14:24 [krit]
ydaniv: Bikeshed does support import information from other specs.
07:15:01 [krit]
ydaniv: Maybe you can ping Tab?
07:15:38 [karlcow]
<edit:with element='rect'>
07:15:45 [karlcow]
<edit:elementsummary name='rect'/>
07:16:00 [karlcow]
https://github.com/w3c/svgwg/blob/c82ab6ad3e1e583744df6c553eb4150477ced399/master/shapes.html#L52

07:17:20 [krit]
karlcow: could you sync with Cameron if there were other use cases for the XML file? Maybe the one time conversion is good enough.
07:17:25 [karlcow]
https://svgwg.org/svg2-draft/shapes.html#RectElement

07:17:58 [krit]
topic: fetch priority to SVG script element
07:18:27 [krit]
viralipurbey: Did we reach a conclusion on this topic or is the discussion still open?
07:19:00 [karlcow]
https://github.com/w3c/svgwg/issues?q=is%3Aissue%20state%3Aopen%20fetchpriority

07:19:08 [viralipurbey]
https://github.com/w3c/svgwg/issues/916

07:20:47 [krit]
Minutes: https://www.w3.org/2025/12/18-svg-minutes.html

07:21:25 [krit]
Vinay: When we supposed the feature to the owner, they were not keen to add this to the parser.
07:21:36 [krit]
s/Vinay/viralipurbey
07:21:50 [Vinay]
https://groups.google.com/a/chromium.org/g/loading-dev/c/abRvsaclp0Q/m/fjLyFZtqDAAJ - Chromium code owners are reluctant to expand their XML-Parser logic thus reluctant to add support for `fetchPriority` in SVG script elements.
07:21:58 [krit]
viralipurbey: Chrome will not support the fetchpriority for now.
07:22:15 [krit]
Vinay: Added a link in the chat to this discussion
07:22:51 [krit]
viralipurbey: I am folllwing up on the action that I had. Our opinion is to not do it.
07:23:17 [krit]
Vinay: It is highly unlikely that we will add that to chrome.
07:23:55 [krit]
RESOLUTION: SVG will not specify the fetchpriority attribute on SVG Script element
07:24:54 [krit]
RRSAgent: make minutes
07:24:55 [RRSAgent]
I have made the request to generate https://www.w3.org/2026/01/08-svg-minutes.html krit
07:25:19 [karlcow]
RRSAgent, make logs public
07:25:27 [krit]
RRSAgent, make logs public