<div dir="ltr">Right. x3dom generates a performance panel and console inside the X3D tag but outside the Scene element (because it does not use an equivalent to x3d-canvas as a wrapper).<div><br></div><div>For tracking purposes, it is probably better to use x_ite.js, not the minimized version.<br><div><br></div><div>One way to have both x3dom and x-ite is to use an iframe to isolate. But for testing it is probably best to just use one or the other, in any case.</div><div><br></div></div><div>-Andreas</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Feb 9, 2023 at 4:12 PM John Carlson <<a href="mailto:yottzumm@gmail.com">yottzumm@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">Hmm, these messages do not affect functionality? Can we move the messages to console.debug?</div><div dir="auto"><br></div><div dir="auto">There maybe something we can do in X3DOM, like checking for enclosing <x3zd-canvas></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Feb 9, 2023 at 7:45 AM Holger Seelig <<a href="mailto:holger.seelig@gmail.com" target="_blank">holger.seelig@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>It is because you have both X_ITE and X3DOM on your page. X_ITE has a <x3d-canvas> element which displays the <X3D> element inside, but X3DOM look for this <X3D> element and makes a canvas out of this and puts some <ul> and <li> and other stuff inside. Now X_ITE is confronted with these elements and throws an error.<div><br></div><div>If you want both X_ITE and X3DOM on you page, it is not easy to do this. I not yet any idea how to do this.</div><div><br></div><div>Best regards,</div><div>Holger</div></div><div><div><br><div><div><blockquote type="cite"><div>Am 09.02.2023 um 13:12 schrieb John Carlson <<a href="mailto:yottzumm@gmail.com" target="_blank">yottzumm@gmail.com</a>>:</div><br><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">I could use some help testing the latest X3DOM and X_ITE in X3DJSONLD.<br></div><div><br></div><div>I've got a whole series of HTML pages to test, some work, some do not.</div><div><br></div><div>This uses the latest unreleased versions of X_ITE and X3DOM, so expect some bumps.</div><div><br></div><div>The idea is to go through these pages, collecting unique errors from the web browser's developer tools console.</div><div><br></div><div>Here is a list of links you can test.</div><div><br></div><div><a href="https://coderextreme.net/X3DJSONLD/src/main/html/codex.html" target="_blank">https://coderextreme.net/X3DJSONLD/src/main/html/codex.html</a><br></div><div><br></div><div>Holger, I'd appreciate if you could peek at:</div><div><br></div><div><a href="https://coderextreme.net/X3DJSONLD/src/main/html/index.html" target="_blank">https://coderextreme.net/X3DJSONLD/src/main/html/index.html</a><br></div><div><br></div><div>Soon, as the errors listed here will go across many pages!</div><div><br></div><div><div>x_ite.min.js:1 </div><div> </div><div> XML Parser Error: Unknown node type 'LI', you probably have insufficient component/profile statements.</div></div><div><br></div><div><br></div></div></div></div></div>
</div></blockquote></div><br></div></div></div></blockquote></div></div>
_______________________________________________<br>
X3dom-users mailing list<br>
<a href="mailto:X3dom-users@lists.sourceforge.net" target="_blank">X3dom-users@lists.sourceforge.net</a><br>
<a href="https://lists.sourceforge.net/lists/listinfo/x3dom-users" rel="noreferrer" target="_blank">https://lists.sourceforge.net/lists/listinfo/x3dom-users</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div>Andreas Plesch<br>Waltham, MA 02453</div></div></div>