The sad state of browser matrix transforms
1–10 of 29 posts
Re: The sad state of browser matrix transforms
#2Re: The sad state of browser matrix transforms
#3I've used the matrix function a lot, and am perfectly happy with how it renders across browsers. I would be happy if it was bug-free and easier to use, but it still gives me a lot more power than if it didn't exist.
Re: The sad state of browser matrix transforms
#4I think saying it's a 'sad state' is a bit dramatic. An 'imperfect state' would be a better description. I've used the matrix function a lot, and am perfectly happy with how it renders across browsers. I would be happy if it was bug-free and easier to use, but it still gives me a lot more power than if it didn't exist.
Re: The sad state of browser matrix transforms
#5How should browsers handle transitions of transformations?
AFAIK in Firefox if your transformation is a composition of multiple transformations then it does a transition of each part in a way where the transformation parameter linearly changes. Like between scale(2) rotate(0) and scale(4) rotate(90) in the middle of the transformation there is scale(3) rotate(45). It's different if you define the same transformations at the two ends as matrices.
It's kind if cool tho, since you can create a transition between rotate(0) and rotate(360), however it's not entirely clear what happens if the two ends have different transformation elements.
Re: The sad state of browser matrix transforms
#6Kind of offtopic: How should browsers handle transitions of transformations? AFAIK in Firefox if your transformation is a composition of multiple transformations then it does a transition of each part in a way where the transformation parameter linearly changes. Like between scale(2) rotate(0) and scale(4) rotate(90) in the middle of the transformation there is scale(3) rotate(45) . It's different if you define the s…
Re: The sad state of browser matrix transforms
#7Kind of offtopic: How should browsers handle transitions of transformations? AFAIK in Firefox if your transformation is a composition of multiple transformations then it does a transition of each part in a way where the transformation parameter linearly changes. Like between scale(2) rotate(0) and scale(4) rotate(90) in the middle of the transformation there is scale(3) rotate(45) . It's different if you define the s…
If all your transforms use the same functions in the same order, then transition is done on arguments of these functions.
If functions or their order differs then everything is flattened to a matrix and then the matrix is transitioned.
Re: The sad state of browser matrix transforms
#8Kind of offtopic: How should browsers handle transitions of transformations? AFAIK in Firefox if your transformation is a composition of multiple transformations then it does a transition of each part in a way where the transformation parameter linearly changes. Like between scale(2) rotate(0) and scale(4) rotate(90) in the middle of the transformation there is scale(3) rotate(45) . It's different if you define the s…
If only mathematicians would construct an algebra of linear transformations. Then the browser vendors could simply implement the laws of this linear algebra once and for all.
Re: The sad state of browser matrix transforms
#9Re: The sad state of browser matrix transforms
#10Kind of offtopic: How should browsers handle transitions of transformations? AFAIK in Firefox if your transformation is a composition of multiple transformations then it does a transition of each part in a way where the transformation parameter linearly changes. Like between scale(2) rotate(0) and scale(4) rotate(90) in the middle of the transformation there is scale(3) rotate(45) . It's different if you define the s…
If only mathematicians would construct an algebra of linear transformations. Then the browser vendors could simply implement the laws of this linear algebra once and for all.
No no, the stuff from the mathematicians probably wouldn't work and we'd be left with a dent in our egos.