Re: [csswg-drafts] [css-transforms-1] Define basis for percentage transform on patterns, gradients, clipPath

The Working Group just discussed `Define basis for percentage transform on patterns, gradients, clipPath`.

<details><summary>The full IRC log of that discussion</summary>
&lt;krit> topic: Define basis for percentage transform on patterns, gradients, clipPath<br>
&lt;BogdanBrinza> GitHub: https://github.com/w3c/csswg-drafts/issues/892<br>
&lt;krit> krit: pattern has patternTransform attribute<br>
&lt;krit> krit: this is mapped to transform property<br>
&lt;krit> krit: which supports percentage<br>
&lt;krit> krit: what do those percentages map too<br>
&lt;krit> krit: currently the spec says they map to the reference box from the transform-box<br>
&lt;krit> AmeliaBR: there are incompatibilities even today<br>
&lt;krit> AmeliaBR: we have different implementations doing different transforms... was never really well defined.<br>
&lt;krit> AmeliaBR: one coordinate. system for tile size, tile content and so on... all use objectBoundingBox or userSpaceOnUse<br>
&lt;krit> krit: even worst, the reference box is different depending if it is content or pattern size<br>
&lt;krit> krit: we also need to decide if the coordinate spaces should be consistent across pattern and mask... extended to work with percentages ... extended to work on clip-path as well.<br>
&lt;krit> krit: AmeliaBR Worte a detailed proposal: https://www.w3.org/Graphics/SVG/WG/wiki/Proposals/Bounding_boxes<br>
&lt;krit> AmeliaBR: is it possible to summarise>?<br>
&lt;krit> AmeliaBR: don't think it is a proposal but rather a summary what is brokeb<br>
&lt;krit> AmeliaBR: for patterns you also want to transform the tiling pattern<br>
&lt;krit> AmeliaBR: like when you transform the root element in a canvas window... like a repeating background image on a root element... when you rotate and scale it the entire canvas rotates and scales... you'd expect something like this for pattenr<br>
&lt;krit> krit: for me that sounds like patternTransform comes before the tile size coordinate system and contnet<br>
&lt;krit> AmeliaBR: it is like grouping, right<br>
&lt;krit> AmeliaBR: but then you need to define the reference size and origin<br>
&lt;krit> AmeliaBR: currently it is not defined in a rich way and browsers are inconsistent<br>
&lt;krit> krit: inconsistent across  all browsers or just certain browsers<br>
&lt;krit> AmeliaBR: last time there were at least3 different versions that cmae<br>
&lt;krit> AmeliaBR: came out<br>
&lt;AmeliaBR> Incompat for SVG patternTransform: https://github.com/w3c/svgwg/issues/293<br>
&lt;krit> krit: is there something we can work on step by step?<br>
&lt;krit> krit: like agree on the transform order?<br>
&lt;krit> krit: for pattern: as if the entire pattern would be grouped and then transformed...<br>
&lt;krit> AmeliaBR: that seems constantly across browsers already<br>
&lt;krit> AmeliaBR: it gets inconsistent when you rotate... what is the origin to rotate around.<br>
&lt;krit> krit: then agree on the order first<br>
&lt;krit> krit: go with "grouping" the entire pattern/mask/clipPath independent of the additional attributes they have...<br>
&lt;krit> BogdanBrinza: not objecting... seems to make sense<br>
&lt;ChrisL> same here, irc and web works but no audio<br>
&lt;BogdanBrinza> let<br>
&lt;BogdanBrinza> let's call in again<br>
&lt;BogdanBrinza> I redialed and doesn't seem that anybody can hear me, right?<br>
&lt;BogdanBrinza> let's quickly capture the last statement to continue smoothly next week<br>
&lt;ChrisL> good idea<br>
&lt;BogdanBrinza> Dirk, was there anything not minuted already?<br>
&lt;BogdanBrinza>  believe the question was on the "grouping" of the patterns/masks/etc and Amelia's opinion on that right?<br>
&lt;krit> correct<br>
&lt;krit> krit: believe the question was on the "grouping" of the patterns/masks/etc and Amelia's opinion on that right?<br>
&lt;AmeliaBR> Last thing I was saying (not sure if any of you heard it): this is another case where we need to write out all the different options (spec-wise), and work through the consequences, to see if they make sense and/or have any compat issues.<br>
&lt;BogdanBrinza> thank you Amelia<br>
&lt;ChrisL> I didn't hear that and yes, I agree<br>
&lt;krit> any action until next weeks call?<br>
&lt;BogdanBrinza> I read Amelia's reply as the action plan<br>
&lt;BogdanBrinza> write down the specific options (ideally with samples) and work through the compatibility impact of each (if any impact at all)<br>
&lt;AmeliaBR> Yep. If anyone can come up with more demos/scenarios (including theoretical examples of features that aren't implemented yet), that would be very helpful.<br>
&lt;AmeliaBR> I'll also call out on Twitter, see if we can get some other opinions from SVG/CSS authors.<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/892#issuecomment-383693455 using your GitHub account

Received on Monday, 23 April 2018 19:26:26 UTC