[Browser-Specific - FF] Latest created surface always on top of older surfaces despite Z-Translate.

[famous]

[Browser-Specific - FF] Latest created surface always on top of older surfaces despite Z-Translate.

[ftripier]

This one's a gecko problem I'm afraid. Bug filed, however:

https://bugzilla.mozilla.org/show_bug.cgi?id=998502

In the meantime, I submitted a pull request for a hotfix into our internal repo that would apply a zindex equal to the the specified z translation on every surface.

[CharlesVoita]

You also have to keep in mind that if the containing element has preserve-3d and is rotated, you must account for rotation; therefore you'd have to calculate based on a surface's distance from a global world point which would require some math. This isn't really an issue now for anyone interested in supporting IE, but may bubble up in the future.

[ftripier]

The final matrices applied to the surface should correctly represent the depth- they get multiplied internally by the browsers rendering engine against the containing elements projection matrix. Our scene graph isn't naive- a rotation matrix multiplied against a translation matrix will produce an output with consistent translation, and vice versa.

To clarify: we'd be mapping from the final matrix before we actually write it to the Surface's html element's internal styles, not as a sum of all z translations applied.

[CharlesVoita]

Apologies!

[MylesBorins]

@ftripier is it safe to close this issue as it is fixed on internal, or should we leave it open until a more permanent solution is found?

[ftripier]

I'd like to leave the issue open in case Charles and/or the community have input down the line. This is a tricky problem, and my current solution is at best a hack.

[jperl]

Chrome also has issues sometimes.

[dmvaldman]

@jperl do you have a perspective defined, or are you in a containerSurface?

[jperl]

@dmvaldman Yes and yes.

[dmvaldman]

you may need to set a perspective on the containerSurface as well, unfortunately we don't expose as API for this yet. Can you try myContainerSurface.context.setPerspective(1000)?

[dmvaldman]

This should be fixed on the most recent release (0.1.2). Would love a confirmation!

[jperl]

@dmvaldman I upgraded famo.us and tried setting the perspective on the containerSurface -- I still need to create the container afterwards for it to be overlaid. However when I try to reproduce this outside of our app I cannot :(. I wonder if it is because I am using meteor to render the div used in the surface. Interestingly it works on firefox and safari.