You could assign the matrixWorld of the scene plane to the object for the css3d renderer and set matrixAutoUpdate to false for it, that saves updating the same matrix twice and you don’t have to synchronize it.
Edit: you’re moving the dom element and not the css3d object btw
This saves your rather expensive updateLabels function, for the drag & drop take a look at the examples for d&d of meshes, so you only deal with your planes. http://jsfiddle.net/Fyrestar/890xgzf7/
You are fully right, I am moving the dom element, not the css3dobject itself.
That was the reason that I was trying to obtain the transformation matrix from the dom object through
csss3dobject.element.style.transform.
The point is that it seems that those transformations are not tracked in the dom element.
Maybe what I am trying makes not sense.
So mean that I should move the mesh plane and not trying to move the dom element?
I can do it by extending the plane and proyect a ray, but I thought that this solution was easier.
By the way, in your example the problem remains and resizing actions don’t update the plane object.
Sorry if I ama bit confussed by your answer, I know that you are very busy withother more important topics and I don’t want to bother you. Just tell me if my second aproach could be a valid solution.
I think I can track these position displacements in my dom elements using properties offsetLeft and offsetTop and adding these displacements in my mesh planes.
Yes the fiddle only improved synchronization. I still wouldn’t recommed any css separate transformations but if it works for you that’s fine i guess