Attribute changes from Chrome Dev Tools are not taken into account

[wherget]

Steps to reproduce:

• open http://xml3d.github.io/xml3d-examples/examples/directionalLight/index.html in Chrome
• open dev tools
• navigate to <group> node with transform="#t_Lamp"
• right click, choose "Add Attribute"
• type visible="false"

Expected Behaviour:

• Scene turns dark

Actual Behaviour:

• nothing happens

Additional Comments:
A similar maneuver using Firebug in Firefox succeeds, as does setting the attribute from Chrome's console when using getElementById() (either using dot-notation or setAttribute). It seems the Dev Tools' Element view writes to the DOM via some means that xml3d.js is not monitoring. It would however be very helpful if this worked, since in web development, rapid iteration using the Dev Tools is a very important technique.

[ksons]

To my knowledge, the Chrome Dev Tools spawn no MutationEvents, which the implementation is listening for. @lachsen started using MutationObservers on branch proto-config (746d541). This might fix the issue.

[lachsen]

Yes, MutationObservers will fix this issue. I think we can merge the proto-config branch to develop soon as everything seems to work so far.

[ksons]

Fixed by 746d541

[ksons]

Included in 4.8 release