Envjs envjs → 1.2.x

Comments and changes to this ticket

• 

  Thatcher February 3rd, 2010 @ 04:43 PM

  • State changed from “new” to “open”
  • Milestone set to “1.2.x”

  This is highest priority fix. 1.2 will not be release until we get this fixed. Look for the test in src/html/document.js when the ticket is closed. Basically we plan to resolve it along with a stateful switch which is triggered by mutation events. There are many cases we hope to codify in the specs. Ideally we can use minimal events. Our choices are:

  case "DOMSubtreeModified":
  case "DOMNodeInserted":
  case "DOMNodeRemoved":
  case "DOMNodeRemovedFromDocument":
  case "DOMNodeInsertedIntoDocument":

  I personally believe we can handle all cases with

  case "DOMNodeRemovedFromDocument":
  case "DOMNodeInsertedIntoDocument":

  and that will be minimal work. The reason is that reasources arent re-loaded(re-executed) unless the node is removed from the document entirely. Plus script nodes after document load arent executed (I think) unless the are appended as children of the head element.
  

  There are additional cases that complicate the issue because the script elements (again I think) shouldnt be executed if they are added via set innerHTML since that is essentially a parser operation/ I believe we can solve this by inspecting a state of the ducument during initial parse vrs later parse.

  Thanks for you patience, this shouldn't have gone unnoticed. Hopefully a series of isolated, clear, simple tests will prevent this from breaking in the future.

  Thatcher

• 

  Thatcher March 4th, 2010 @ 12:38 AM

  this is fixed an unit tested in 1.2.0.1

• 

  Thatcher March 4th, 2010 @ 10:58 AM

  • State changed from “open” to “resolved”