Document.renameNode seems cool. Aside from the awkward user data event, it matches perfectly the needs of the Component Model (updated to reference it here: http://wiki.whatwg.org/wiki/Component_Model#Performance).
I am curious why no one had implemented this. We should dust it off, add a normal event to it, and set it sail. :DG< On Mon, Aug 29, 2011 at 2:07 PM, Boris Zbarsky <[email protected]> wrote: > On 8/29/11 4:53 PM, Robin Berjon wrote: >> >> On Aug 29, 2011, at 21:40 , Boris Zbarsky wrote: >>> >>> On 8/29/11 3:33 PM, Robin Berjon wrote: >>>> >>>> For completeness, I'm guessing that namespaces would be supported as >>>> well? >>>> >>>> Element renameElement(DOMString newName); >>>> Element renameElement(DOMString newNS, DOMString newName); >>> >>> Shades of >>> http://www.w3.org/TR/DOM-Level-3-Core/core.html#Document3-renameNode >> >> Yeah, but my recollection is that renameNode() is in the list of DOM >> things that are so hopelessly fuzzy that you probably don't want to touch >> them if you plan on being interoperable. Rereading the description after not >> having touched it in years certainly reinforces that feeling. > > Sure. I wasn't exactly endorsing it; just pointing to previous attempts to > spec such a thing in case they would be useful. > > -Boris > >
