Bug 733849 Comment 15 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Yes, adding `transform-style: inherit` into `-moz-table-wrapper` makes everything disappear. And got an assertion if I add `transform-style: inherit` into `-moz-cell-content`.

One thing to note: WebKit may also have something wrong in the similar cases. It doesn't pass the wpt, and have some strange behaviors if the combined rotateX() is more than 90deg. (Not sure what happens. It looks like Gecko has the similar behavior.)

Besides, in the frame tree, I notice `TableRowGroup(tbody)` doesn't have `combines-3d-transform-with-ancestors`. This may be a hint that it doesn't combine its 3d context with its ancestor. Need to dig deeper anyway.
Yes, adding `transform-style: inherit` into `-moz-table-wrapper` makes everything disappear. And got an assertion if I add `transform-style: inherit` into `-moz-cell-content`.

One thing to note: WebKit may also have something wrong in the similar cases. It doesn't pass the wpt, and have some strange behaviors if the combined `rotateX()` is more than `rotateX(90deg)`. (Not sure what happens. It looks like Gecko has the similar behavior.)

Besides, in the frame tree, I notice `TableRowGroup(tbody)` doesn't have `combines-3d-transform-with-ancestors`. This may be a hint that it doesn't combine its 3d context with its ancestor. Need to dig deeper anyway.
Yes, adding `transform-style: inherit` into `-moz-table-wrapper` makes everything disappear. And got an assertion if I add `transform-style: inherit` into `-moz-cell-content`.

One thing to note: WebKit may also have something wrong in the similar cases. It doesn't pass the wpt, and have some strange behaviors if the combined `rotateX()` is more than `rotateX(90deg)`. (Not sure what happens. It looks like Gecko has the similar behavior, so I have to tweak the test to make sure the combined rotation is less than 90deg.)

Besides, in the frame tree, I notice `TableRowGroup(tbody)` doesn't have `combines-3d-transform-with-ancestors`. This may be a hint that it doesn't combine its 3d context with its ancestor. Need to dig deeper anyway.
Yes, adding `transform-style: inherit` into `-moz-table-wrapper` makes everything disappear. And got an assertion if I add `transform-style: inherit` into `-moz-cell-content`.

One thing to note: WebKit may also have something wrong in the similar cases. It doesn't pass the wpt, and have some strange behaviors if the combined `rotateX()` is more than `rotateX(90deg)`. (Not sure what happens. It looks like Gecko has the similar behavior, so I have to tweak the test to make sure the combined rotateX is less than 90deg.)

Besides, in the frame tree, I notice `TableRowGroup(tbody)` doesn't have `combines-3d-transform-with-ancestors`. This may be a hint that it doesn't combine its 3d context with its ancestor. Need to dig deeper anyway.
Yes, adding `transform-style: inherit` into `-moz-table-wrapper` makes everything disappear. And got an assertion if I add `transform-style: inherit` into `-moz-cell-content`.

One thing to note: WebKit may also have something wrong in the similar cases. It doesn't pass the wpt, and have some strange behaviors if the combined `rotateX()` is more than `rotateX(90deg)`. (Not sure what happens. It looks like Gecko has the similar behavior, so I have to tweak the test to make sure the combined rotateX is less than 90deg.)

Besides, in the frame tree, I notice `TableRowGroup(tbody)` doesn't have `combines-3d-transform-with-ancestors`. This may be a hint that it doesn't combine its 3d context with its ancestor. (So I tried to move the outer `rotateX()` from outer `div` into `tbody`. Well, it looks normal, if the combined rotation is less than 90deg.) Need to dig deeper anyway.
Yes, adding `transform-style: inherit` into `-moz-table-wrapper` makes everything disappear. And got an assertion if I add `transform-style: inherit` into `-moz-cell-content`.

One thing to note: WebKit may also have something wrong in the similar cases. It doesn't pass the wpt, and have some strange behaviors if the combined `rotateX()` is more than `rotateX(90deg)`. (Not sure what happens. It looks like Gecko has the similar behavior, so I have to tweak the test to make sure the combined rotateX is less than 90deg.)

Besides, in the frame tree, I notice `TableRowGroup(tbody)` doesn't have `combines-3d-transform-with-ancestors`. This may be a hint that it doesn't combine its 3d context with its ancestor. (So I tried to move the outer `rotateX()` from outer `div` into `tbody`. Well, the result becomes correct, if the combined rotation is less than 90deg.) Need to dig deeper anyway.
Yes, adding `transform-style: inherit` into `-moz-table-wrapper` makes everything disappear. And got an assertion if I add `transform-style: inherit` into `-moz-cell-content`.

One thing to note: WebKit may also have something wrong in the similar cases. It doesn't pass the wpt, and have some strange behaviors if the combined `rotateX()` is more than `rotateX(90deg)`. (Not sure what happens. It looks like Gecko has the similar behavior, so I have to tweak the test to make sure the combined rotateX is less than 90deg.)

Besides, in the frame tree, I notice `TableRowGroup(tbody)` doesn't have `combines-3d-transform-with-ancestors`. This may be a hint that it doesn't combine its 3d context with its ancestor. (So I tried to move the outer `rotateX()` from outer `div` into `tbody`. Well, the result becomes correct, if the combined rotation is less than 90deg.) Need to dig deeper anyway.

UPDATE:
It looks like `preserve-3d` doesn't work on table element. `IsExtend3D()` always return false because `mTransoformStyle` is always flat, even if we set the style to `preserve-3d`. I tried to hack it to make it return true in this function, but the element inside the table disappears, just like bug 1560704.
Yes, adding `transform-style: inherit` into `-moz-table-wrapper` makes everything disappear. And got an assertion if I add `transform-style: inherit` into `-moz-cell-content`.

One thing to note: WebKit may also have something wrong in the similar cases. It doesn't pass the wpt, and have some strange behaviors if the combined `rotateX()` is more than `rotateX(90deg)`. (Not sure what happens. It looks like Gecko has the similar behavior, so I have to tweak the test to make sure the combined rotateX is less than 90deg.)

Besides, in the frame tree, I notice `TableRowGroup(tbody)` doesn't have `combines-3d-transform-with-ancestors`. This may be a hint that it doesn't combine its 3d context with its ancestor. (So I tried to move the outer `rotateX()` from outer `div` into `tbody`. Well, the result becomes correct, if the combined rotation is less than 90deg.) Need to dig deeper anyway.

UPDATE:
It looks like `preserve-3d` doesn't work on table element. `IsExtend3D()` always returns false because `mTransoformStyle` is always flat, even if we set the style to `preserve-3d`. I tried to hack it to make it return true in this function, but the element inside the table disappears, just like bug 1560704.
Yes, adding `transform-style: inherit` into `-moz-table-wrapper` makes everything disappear. And got an assertion if I add `transform-style: inherit` into `-moz-cell-content`.

One thing to note: WebKit may also have something wrong in the similar cases. It doesn't pass the wpt, and have some strange behaviors if the combined `rotateX()` is more than `rotateX(90deg)`. (Not sure what happens. It looks like Gecko has the similar behavior, so I have to tweak the test to make sure the combined rotateX is less than 90deg.)

Besides, in the frame tree, I notice `TableRowGroup(tbody)` doesn't have `combines-3d-transform-with-ancestors`. This may be a hint that it doesn't combine its 3d context with its ancestor. (So I tried to move the outer `rotateX()` from outer `div` into `tbody`. Well, the result becomes correct, if the combined rotation is less than 90deg.) Need to dig deeper anyway.

UPDATE:
It looks like `preserve-3d` doesn't work on table element. `IsExtend3D()` always returns false because its `mTransoformStyle` is always flat, even if we set the style to `preserve-3d`. I tried to hack it to make it return true in this function, but the element inside the table disappears, just like bug 1560704.
Yes, adding `transform-style: inherit` into `-moz-table-wrapper` makes everything disappear. And got an assertion if I add `transform-style: inherit` into `-moz-cell-content`.

One thing to note: WebKit may also have something wrong in the similar cases. It doesn't pass the wpt, and have some strange behaviors if the combined `rotateX()` is more than `rotateX(90deg)`. (Not sure what happens. It looks like Gecko has the similar behavior, so I have to tweak the test to make sure the combined rotateX is less than 90deg.)

Besides, in the frame tree, I notice `TableRowGroup(tbody)` doesn't have `combines-3d-transform-with-ancestors`. This may be a hint that it doesn't combine its 3d context with its ancestor. (So I tried to move the outer `rotateX()` from outer `div` into `tbody`. Well, the result becomes correct, if the combined rotation is less than 90deg.) Need to dig deeper anyway.

UPDATE:
It looks like `preserve-3d` doesn't work on table element. `IsExtend3D()` always returns false because its `mTransoformStyle` is always flat, even if we set the style to `preserve-3d`. I tried to hack it to make it return true in this function, but the element inside the table element disappears, just like bug 1560704.
Yes, adding `transform-style: inherit` into `-moz-table-wrapper` makes everything disappear. And got an assertion if I add `transform-style: inherit` into `-moz-cell-content`.

One thing to note: WebKit may also have something wrong in the similar cases. It doesn't pass the wpt, and have some strange behaviors if the combined `rotateX()` is more than `rotateX(90deg)`. (Not sure what happens. It looks like Gecko has the similar behavior, so I have to tweak the test to make sure the combined rotateX is less than 90deg.)

Besides, in the frame tree, I notice `TableRowGroup(tbody)` doesn't have `combines-3d-transform-with-ancestors`. This may be a hint that it doesn't combine its 3d context with its ancestor. (So I tried to move the outer `rotateX()` from outer `div` into `tbody`. Well, the result becomes correct, if the combined rotation is less than 90deg.) Need to dig deeper anyway.

UPDATE:
It looks like `preserve-3d` doesn't work on table element. `IsExtend3D()` always returns false because its `mTransoformStyle` is always flat, even if we set the style to `preserve-3d`. I tried to hack it to make it return true in this function, but the element inside the table element disappears, just like bug 1560704. And so I suspect Bug 928322 is duplicated by this bug.
Yes, adding `transform-style: inherit` into `-moz-table-wrapper` makes everything disappear. And got an assertion if I add `transform-style: inherit` into `-moz-cell-content`.

One thing to note: WebKit may also have something wrong in the similar cases. It doesn't pass the wpt, and have some strange behaviors if the combined `rotateX()` is more than `rotateX(90deg)`. (Not sure what happens. It looks like Gecko has the similar behavior, so I have to tweak the test to make sure the combined rotateX is less than 90deg.)

Besides, in the frame tree, I notice `TableRowGroup(tbody)` doesn't have `combines-3d-transform-with-ancestors`. This may be a hint that it doesn't combine its 3d context with its ancestor. (So I tried to move the outer `rotateX()` from outer `div` into `tbody`. Well, the result becomes correct, if the combined rotation is less than 90deg.) Need to dig deeper anyway.
Yes, adding `transform-style: inherit` into `-moz-table-wrapper` makes everything disappear. And got an assertion if I add `transform-style: inherit` into `-moz-cell-content`.

One thing to note: WebKit may also have something wrong in the similar cases. It doesn't pass the wpt, and have some strange behaviors if we use `rotateX(90deg)` in the outer div. (Not sure what happens. It looks like Gecko has the similar behavior, so I have to tweak the test to make sure the combined rotateX is less than 90deg.)

Besides, in the frame tree, I notice `TableRowGroup(tbody)` doesn't have `combines-3d-transform-with-ancestors`. This may be a hint that it doesn't combine its 3d context with its ancestor. (So I tried to move the outer `rotateX()` from outer `div` into `tbody`. Well, the result becomes correct, if the combined rotation is less than 90deg.) Need to dig deeper anyway.

Back to Bug 733849 Comment 15