You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we create a <canvas> element and place it at the <xml3d> element's DOM position. This implicit mutation of the DOM is not very elegant and might confuse an application.
With Shadow DOM functionality we can hide the canvas inside the <xml3d> element's shadow tree. Hence we would not have to modify the (exposed) DOM.
Unfortinately, only a small subset of browsers support Shadow DOM. One could use the Shadow DOM where available and, at the same time, provide a unified access to the <canvas> element (e.g. as a property of the <xml3d> element).
The text was updated successfully, but these errors were encountered:
Currently we create a
<canvas>
element and place it at the<xml3d>
element's DOM position. This implicit mutation of the DOM is not very elegant and might confuse an application.With Shadow DOM functionality we can hide the canvas inside the
<xml3d>
element's shadow tree. Hence we would not have to modify the (exposed) DOM.Unfortinately, only a small subset of browsers support Shadow DOM. One could use the Shadow DOM where available and, at the same time, provide a unified access to the
<canvas>
element (e.g. as a property of the<xml3d>
element).The text was updated successfully, but these errors were encountered: