[x3d-public] Collecting error messages (X3DJSONLD in testing period)

[John Carlson]

Hmm, these messages do not affect functionality?   Can we move the messages
to console.debug?

There maybe something we can do in X3DOM, like checking for enclosing
<x3zd-canvas>

On Thu, Feb 9, 2023 at 7:45 AM Holger Seelig <holger.seelig at gmail.com>
wrote:

> 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.
>
> 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.
>
> Best regards,
> Holger
>
> Am 09.02.2023 um 13:12 schrieb John Carlson <yottzumm at gmail.com>:
>
> I could use some help testing the latest X3DOM and X_ITE in X3DJSONLD.
>
> I've got a whole series of HTML pages to test, some work, some do not.
>
> This uses the latest unreleased versions of X_ITE and X3DOM, so expect
> some bumps.
>
> The idea is to go through these pages, collecting unique errors from the
> web browser's developer tools console.
>
> Here is a list of links you can test.
>
> https://coderextreme.net/X3DJSONLD/src/main/html/codex.html
>
> Holger, I'd appreciate if you could peek at:
>
> https://coderextreme.net/X3DJSONLD/src/main/html/index.html
>
> Soon, as the errors listed here will go across many pages!
>
> x_ite.min.js:1
>
>        XML Parser Error: Unknown node type 'LI', you probably have
> insufficient component/profile statements.
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20230209/5e33707c/attachment.html>