On Dec 20, 2007 11:49 AM, Kurt Cagle <[EMAIL PROTECTED]> wrote: > There was a change in the underlying DOM that will likely have a lot of > people unhappy - the introduction of importNode() and adoptNode(). More info > at > http://developer.mozilla.org/en/docs/Updating_web_applications_for_Firefox_3
Thanks for the link. If I'm reading that right, nodes from external DOMs need to be imported or adopted; does this mean that a newly created element is considered to be from an external DOM? A little bit funky. On Dec 20, 2007 1:55 PM, kangax <[EMAIL PROTECTED]> wrote: > Indeed, if you run DOM unit tests, testElementUpdateWithDOMNode fails > with NS_ERROR_DOM_RANGE_INVALID_NODE_TYPE_ERR error. On line 2505 (as > of rev 8451) "range.selectNodeContents(element)" seems to dislike > passed element. Well, that's good to know; thanks for the info, kangax. Does that mean this is something that's going to be fixed in Prototype? Thanks again for the replies! :Dan Dorman --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
