23705 2013-11-01 16:23:49 +0000 MutationObserver observe option validation does not match implementations 2013-11-01 17:43:42 +0000 1 1 1 Unclassified WebAppsWG DOM unspecified All All RESOLVED WONTFIX P2 normal --- 1 erik.arvidsson annevk bugs bzbarsky mike www-dom public-webapps-bugzilla oldest_to_newest 95688 0 erik.arvidsson 2013-11-01 16:23:49 +0000 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. 95689 1 annevk 2013-11-01 16:41:00 +0000 Do you disagree with bug 23189? 95691 2 erik.arvidsson 2013-11-01 17:02:12 +0000 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. 95692 3 annevk 2013-11-01 17:08:37 +0000 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. 95702 4 erik.arvidsson 2013-11-01 17:41:48 +0000 Agreed.