Re: [dom] setAttributeNode should not change order of existing attributes (#116) from Anne van Kesteren on 2016-01-01 (public-webapps-github@w3.org from January 2016)

From: Anne van Kesteren <notifications@github.com>
Date: Fri, 01 Jan 2016 06:12:13 -0800
To: whatwg/dom <dom@noreply.github.com>
Message-ID: <whatwg/dom/issues/116/168309086@github.com>

Judging from https://github.com/servo/servo/pull/9061#issuecomment-167796252 all browsers have a "replace" algorithm here and issue a single mutation record. Gecko just implements the replacing via remove/append, whereas everyone else does an actual replace. Given that we should just do the replacing thing. Adjusting @nox' PR will get us there.

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

Received on Friday, 1 January 2016 14:12:48 UTC