- From: goldenboy777 via GitHub <noreply@w3.org>
- Date: Mon, 04 Aug 2025 08:57:50 +0000
- To: public-css-archive@w3.org
Hi @longsonr, just wanted some clarification: >I don't think we agree with the way forward with nested SVG sizing tests and I'm not sure we'd change our implementation any time soon (if at all). is the disagreement mainly due to the viewport units(vw,vh etc) proposal and related test cases? or all the newly introduced test cases have similar problem?? I agree with the redundancy with the percentage units with our proposal for viewport units I think a similar concern was raised in one of the earlier comments. I have also verified that currently Chromium also a similar implementation as you mentioned w.r.t vw, vh units. > vw and vh would always be a percentage of the viewport. Our proposal was mainly due to the ambiguity in what "viewport" (SVG viewport or browser viewport) should be selected. We can update the tentative viewport units related tests and our proposal to incorporate the browser viewport rather than SVG viewport, will that align more with Firefox implementation as well?? I would also like to confirm that the below SVG utilize the browser viewport for nested `svg` element (both in Chrome and Firefox) ``` <svg width="100" height="100" xmlns="http://www.w3.org/2000/svg"> <svg width="5vw" height="5vh"> <circle cx="50" cy="50" r="40" fill="green" /> </svg> </svg> ``` However, the output of above SVG is not identical to the below one when instead styles are passed: ``` <svg width="100" height="100" xmlns="http://www.w3.org/2000/svg"> <svg style="width:5vw;height:5vh"> <circle cx="50" cy="50" r="40" fill="green" /> </svg> </svg> ``` -- GitHub Notification of comment by goldenboy777 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12376#issuecomment-3149711910 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 4 August 2025 08:57:50 UTC