- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Mon, 27 Aug 2018 20:20:27 +0000
- To: public-svg-issues@w3.org
The SVG Working Group just discussed `Review property value definitions to ensure unitless lengths are correctly included`, and agreed to the following: * `RESOLUTION: Ask the CSS WG for feedback on number length values for currently SVG specific CSS propertoes` <details><summary>The full IRC log of that discussion</summary> <krit> topic: Review property value definitions to ensure unitless lengths are correctly included<br> <krit> GitHub: https://github.com/w3c/svgwg/issues/534<br> <krit> ericwilligers: The google docs demonstrates which properties in implementations currently support length and number values as length: https://docs.google.com/spreadsheets/d/1HRzb_-S28xq7GqYKhHbMP2YQlqWLvOWSS_twLXy-I40/edit#gid=1297517027<br> <krit> ericwilligers: we need to look at the properties which we are going to change in the implementations and which in the specification like stroke-dash-array<br> <krit> AmeliaBR: those were defined in SVG 1. though it was redefined by CSS and we need to propose changes to the CSS WG.<br> <krit> AmeliaBR: for the geometry properties, thet are SVG specific and already ship in multiple properties I am happy to add the plain numbers for them<br> <krit> krit: there would be some inconsistencies for instance with width and height which do not support numbers.<br> <krit> krit: also, the layout properties currently are SVG specific but might not be in the future.<br> <krit> ericwilligers: we could say that those are in the quirks mode for SVG.<br> <krit> krit: IIRC there is no official quirks mode yet<br> <AmeliaBR> Usage data: https://developer.microsoft.com/en-us/microsoft-edge/platform/usage/css/cx/<br> <krit> krit: I'd suggest that we look if the cx, cy and so on properties could change to length only values<br> <krit> krit: seems like 20% are number versions<br> <krit> krit: I guess we have to decide case by case then<br> <krit> ericwilligers: but the numbers are all very very slow<br> <krit> krit: that is true<br> <krit> krit: starting with the layout properties first... anyone we want to reach out to or investigate?<br> <krit> AmeliaBR: we could bring this up as part of CSS discussions.<br> <krit> AmeliaBR: especially with being consistent with width and height and already shipping presentation attributes.<br> <krit> krit: we already have differences between attribute and property value definition so that by itself is not argument for number values on properties.<br> <krit> AmeliaBR: yes<br> <krit> krit: could we send the document to the CSS WG and ask for their feedback?<br> <krit> ericwilligers: I prepared it already and can present to the CSS WG<br> <krit> AmeliaBR: for the stroke-* properties this is just a correction but the other properties are more of a debate.<br> <krit> RESOLUTION: Ask the CSS WG for feedback on number length values for currently SVG specific CSS propertoes<br> <krit> s/propertoes/properties/<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/svgwg/issues/534#issuecomment-416355211 using your GitHub account
Received on Monday, 27 August 2018 20:20:28 UTC