Took us a while to figure this one out, sorry for the delay.
First things first, it worked with A-Frame just fine as this glitch demonstrates. The fact that the position and rotation don't show up in source code doesn't mean they don't work.
The reason for that is that A-Frame turns the attribute values into objects and objects aren't displayed in HTML sourcecode as (per standard) attribute values have to be strings. The fact that they aren't is not caused by us but by A-Frame and is, in fact, not a problem normally - it's the opposite as it is an optimisation.
Now you might want to show the information as part of an HTML dump (e.g. by displaying innerHTML
in a textarea
, then this is a problem.
That problem can be overcome by calling flushToDOM
on the elements, like in this glitch. This affects all dynamically created A-Frame elements, not only 3d.io elements, by the way - you see this with the box element.
I hope this answers your question?