Re: [dom] setAttributeNode should not change order of existing attributes (#116)

I think that is fine personally, since mutation observers do not treat attributes as proper objects. However, I'm still wondering why we'd want to introduce this additional complexity for such an unused method. I guess because three out of four browsers already do it...

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/116#issuecomment-159231991