This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
http://dom.spec.whatwg.org/#dom-mutationobserver-observe Given: observe(node, {attributeOldValue: true}) now in step 1 `attributes` gets set to true, therefore making 3 no longer throw. This does not match WebKit/Blink, Gecko nor IE. Removing step 1 and 2 seems to match implementations better.
Do you disagree with bug 23189?
I did not know the spec intentionally did this to allow skipping setting attributes and characterData when dependent options are present. Seems like a good goal but with 4 browsers requiring attributes to be present and true I'm not sure it is worth it.
The benefit would be long term. And relatively short term if you only care about Chrome and Firefox... Seems we always talk about developer ergonomics and this is a rather cheap change to get there.
Agreed.