[X3D-Ecosystem] X3DOM + React, a possible way forward

[John Carlson]

Here’s the stackoverflow (not the accepted answer):
https://stackoverflow.com/questions/48751919/how-can-i-suppress-the-tag-some-tag-is-unrecognized-in-this-browser-warning

Apparently, is=“whatever” in HTML (and X3DOM nodes) works to suppress
errors.

On Wed, May 7, 2025 at 9:15 AM John Carlson <yottzumm at gmail.com> wrote:

> Not making X3D work with React seems like a major defeat, but there
> appears to be a way forward:
>
> 1.  Convert X3D to x3dom.  Lowercase tags and attributes.
> 2. Add is=“x3d” to every x3dom node and statement converted.
> 3.  Place x3d in a react component.
>
> There’s a few murmuring of it on the web.
>
> I can certainly do 2 and 3 if needed.  Perhaps someone could do 1 and 2?
> Are they already done?
>
> I can do spot test checking as well.
>
> John
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-ecosystem_web3d.org/attachments/20250507/3ef6836c/attachment.html>