[x3d-public] containerField modifications by script

[Andreas Plesch]

There may be rare circumstances when an application may want to modify the
containerField value of an existing x3d node although I am not sure if this
is ever a concern.

So for cobweb_dom, I do think mutations to the containerField attribute may
only need to lead to a warning that such is not supported and ignored.

Unless there is some situation where this would be valuable ? An
application can always delete the x3d node (causing a set_ event to
defaults) and then add a new x3d node in place (causing a set_ event to the
new value).

-Andreas
-- 
Andreas Plesch
39 Barbara Rd.
Waltham, MA 02453
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20161026/04b214fd/attachment.html>