Attribute changes from Chrome Dev Tools are not taken into account

wherget commented 10 years ago

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 commented 10 years ago

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

lachsen commented 10 years ago

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 commented 9 years ago

Fixed by 746d541

ksons commented 9 years ago

Included in 4.8 release

xml3d / xml3d.js

Attribute changes from Chrome Dev Tools are not taken into account #74