[x3d-public] unmatched xxxTextureMapping

[Andreas Plesch]

As
https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4.1-CD/Part01/components/shape.html#TextureMappingCoordinate

and co. explains the xxxTextureMapping field can be used to have multiple
sets/channels of TextureCoordinates for the same Shape, for different types
of Textures.

There is one case which is not covered, presumably because it typically
would indicate a mistake or oversight by the author. What should a browser
implementation do if a material has a (non-default) xxxTextureMapping which
does not match any of the provided TextureCoordinates for the Shape ?

Possibilities are fall-back to default texture coordinates, fall-back to
the first provided mapping, fall-back to constant uv 0,0 to indicate
visually a problem, or undefined behaviour.

Undefined behaviour might be ok but it is then worth pointing out in the
spec.

Thanks, -Andreas

-- 
Andreas Plesch
Waltham, MA 02453
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20250221/c8b77b0e/attachment.html>