06:35:27 RRSAgent has joined #svg 06:35:31 logging to https://www.w3.org/2026/03/05-svg-irc 06:42:58 krit has joined #svg 06:43:07 Zakim has joined #svg 06:44:13 Meeting: SVG WG 06:44:29 present+ 06:44:33 Chair: Dirk Schulze 06:44:51 Agenda: https://github.com/w3c/svgwg/issues?q=is%3Aissue%20state%3Aopen%20label%3AAgenda%2B 06:44:53 dmangal has joined #svg 06:45:11 Vinay has joined #svg 06:45:27 nzimmermann has joined #svg 06:45:33 present+ 06:45:39 present+ 06:46:38 scribe: krit 06:47:01 topic: Remove "side" attribute from "textPath" 06:47:13 https://github.com/w3c/svgwg/issues/1068 06:47:23 present+ 06:48:28 present+ Carine 06:51:23 karlcow: I was under the impression that this hasn't been implemented. Just now I see a comment from chromium that implementation is under way. 06:52:02 nzimmermann: I would vote for keeping it. Just another transformation on top of text length and other transformation attributes. I would recommend to keep it. 06:52:17 viralipurbey has joined #svg 06:52:27 present+ 06:52:41 krit: IMO we would also need to test SVG viewers if they might have implemented it already, like InkScape. Illustrator does not plan to implement though. 06:53:02 Vinay: Is it a series of operations? 06:53:31 nzimmermann: yes, each glyph needs to get transformed. But we do that already for the other transformations. 06:53:45 Vinay: doesn't seem chalanging implementation wise but we need to see usage. 06:54:09 viralipurbey: Agree, we need to evaluate if users adapt it. 06:54:47 nzimmermann: it is convenient and not required. I don't have a strong opinion. 06:55:02 Vinay: Unlikely for developers have a use case. 06:55:26 https://chromium-review.googlesource.com/c/chromium/src/+/7485663 06:56:14 krit: Lets post pone decision to next week until we know actual implementation status. 06:56:22 karlcow: need more WPT test cases. 06:56:59 topic: Remove shape-inside and shape-substract from SVG2 06:57:05 https://github.com/w3c/svgwg/issues/1067 06:57:36 karlcow: Looking at the tests it doesn't seem to be implemented. 06:58:31 krit: This is about wrapping text in shapes based on the CSS implementation in HTML 06:58:51 krit: I know that FF supports text wrap in a block for SVG. Any other implementation? 06:59:00 Vinay: Not in chrome 06:59:06 viralipurbey: no there isn't 06:59:54 krit: I am not even sure if we even have detailed enough spec text to implement wrapping reliably 07:00:01 karlcow: I'd suppose to drop it. 07:00:48 nzimmermann: touching text in browsers is tricky. If it hasn't been implemented so far, it is unlikely to still get implemented. 07:01:24 wrapping is general is pretty desirable by the community https://github.com/w3c/svgwg/issues/942 07:01:28 nzimmermann: uncharted territory. Even today, text/text selection is underspecified. This adds more friction. 07:01:46 nzimmermann: we already tried multi-line text earlier and it was a nightmare. 07:02:14 dmangal: Nevertheless, seems desirable and users ask for it. From implementation point of view I agree though. 07:02:20 Ragvesh has joined #svg 07:02:27 present+ 07:04:02 krit: I hear no commitment from participants to implement. We don't know to which extend the FF implementation is complete, what do we want to do? 07:04:31 karlcow: advocating for finishing SVG2 and drop it from current spec. 07:05:18 dmangal: I'd like to ask for more time to test in Chrome and get back. 07:07:02 nzimmermann: 25 years ago was meant to be standalone. Nowadays we are phasing user demands but as a web developer I'd think of a compound document. That is why there is the demand is probably coming from. But as a standalone document, SVG2 should limit to itself and omit and avoid complexity and rather defer to compound documents. 07:07:37 dmangal: I agree. We should scope from SVG point of view. Layout structure is very differnt in SVG. 07:07:55 dmangal: If needed we can add it to a compound document or another draft. 07:08:20 nzimmermann: this is a multi-month effort and I'd vote to drop it. 07:08:31 dmangal: agree. 07:09:14 RESOLUTION: Drop text wrapping in CSS shapes for SVG2 07:09:42 topic: Remove stroke-linejoin 'miter-clip' or 'arcs' 07:09:51 https://github.com/w3c/svgwg/issues/1065 07:10:30 karlcow: The current WPT test cases seem to fail everywhere. 07:10:46 karlcow: There is a comment in the spec that there are no browser implementations. 07:12:13 krit: My concern, even at the time, was that rendering libraries do not support this. So it needs to be implemented in browsers. Something browsers do not do toay. 07:12:45 nzimmermann has joined #svg 07:12:53 nzimmermann: it would also kill performance. Easy to add if rendering engines/libraries would support it but this is not the case and would be very complex to implement on browser level. Likely never ever going to happen. 07:13:41 krit: do we want to get to a resolution to drop it? Or defer it? 07:14:42 Vinay: We should not complicate SVG 2 for now and may keep it for later. 07:15:43 nzimmermann: it is greatly written for libraries though. But even that description is very difficult to implement due to the edge cases. 07:15:59 RESOLUTION: Drop 'miter-clip' or 'arcs' from SVG 2 07:16:13 topic: UA stylesheet seems to require title as display: none but browsers do display: inline 07:16:21 https://github.com/w3c/svgwg/issues/828 07:16:38 karlcow: This UA stylesheet is not implemented in any browser. 07:16:53 krit: you mean this particular property. 07:17:28 karlcow: I don't believe it is part of any implementation, yes. 07:19:01 nzimmermann: I'd like to clarify that UA stylesheets for SVG do exist (unlike the last comment on the git ticket suggests). It is just this setting that is not implemented. 07:20:08 dmangal: I believe display inline/none makes no sense in the referenced issue make sense for rendering. So I would recommend to drop the entire display section from the spec. 07:22:20 krit: I get from the discussion that we should not require browsers to adapt to a UA stylesheet that is the same everywhere as there are browser specific settings that browsers need to look for. So lets focus on properties that must be part of the UA and not require a specific form. 07:23:38 RESOLUTION: Drop display: inline AND display: none from SVG 2 in the UA stylesheet as requirement 07:23:56 topic: Does the entire path need to be valid in order to use a path attribute on a textPath 07:24:08 https://github.com/w3c/svgwg/issues/393 07:24:41 viralipurbey: continuation of previous discussion. We decided, that viewers should not take href in case of errors. 07:25:35 viralipurbey: when working on WPT I saw the comment on the fallback and wanted to confirm what the spec text should say. 07:26:34 nzimmermann: literally taken it would never fallback to href. 07:26:39 https://w3c.github.io/svgwg/svg2-draft/paths.html#PathDataErrorHandling 07:27:31 krit: Last resolution was that: if there is a d attribute, do not fallback to href. 07:27:39 viralipurbey: We need to be clear in the spec. 07:27:51 nzimmermann: yes, remove that part that you pointed out from the spec. 07:28:28 https://w3c.github.io/svgwg/svg2-draft/text.html#:~:text=If%20the%20‘path’%20attribute%20contains%20an%20error%2C%20the%20‘href’%20attribute%20must%20be%20used. 07:30:28 viralipurbey: I am concerned that we didn't catch the original intend. 07:30:54 viralipurbey: Since an empty path is a valid path, we should not fallback. But why was it introduced then? 07:34:06 ACTION: karlcow and viralipurbey to check what browsers do based on the original WPT tests. 07:35:27 RRSAgent, make minutes 07:35:28 I have made the request to generate https://www.w3.org/2026/03/05-svg-minutes.html krit 07:35:43 RRSAgent, make minutes public 07:35:43 I'm logging. I don't understand 'make minutes public', krit. Try /msg RRSAgent help 07:35:53 RRSAgent, make logs public 07:36:16 krit, Thanks a lot for the scribing. 07:36:25 :) 12:16:58 Zakim has left #svg 12:17:22 zrhoffman1 has joined #svg