- From: Dirk Schulze via GitHub <sysbot+gh@w3.org>
- Date: Fri, 01 Jun 2018 18:50:05 +0000
- To: public-css-archive@w3.org
@tabatkins Oh got it. The common [transform function primitive](https://drafts.csswg.org/css-transforms/#transform-primitives) is there already and [adding neutral transform functions at the end of the list](https://drafts.csswg.org/css-transforms/#transform-transform-neutral-extend-animation) was added recently. The proposal in https://github.com/w3c/csswg-drafts/issues/927#issue-200763204 and the question from @birtles https://github.com/w3c/csswg-drafts/issues/927#issuecomment-392390666 goes adds an additional step: If there is a mismatch between 2 transform function pairs (no common primitive): Instead of multiplying all transform functions into one matrix before decomposing the suggestion is to do the matrix interpolation part only between not matching transform function pairs. An additional question I have for that proposal: `rotate(180deg) translate(120px) scale(2)` -> `rotate(180deg) scale(2) skewX(45deg)`. According to the proposal, `rotate` uses normal interpolation for rotate: * Would the 2nd and 3rd transform functions get multiplied first before the matrix interpolation happens or does it happen per transform function pair? Matrix decomposition and recomposition involves a lot of operations. Doing it for each function pair might be too expensive. The order of multiplication matters. * If we collapse multiple not-matching transform function pairs before matrix interpolation, would it happen up to the next matching function pair or do we just do it for the entire rest of the transform function lists? -- GitHub Notification of comment by dirkschulze Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/927#issuecomment-393976109 using your GitHub account
Received on Friday, 1 June 2018 18:50:09 UTC