4567 2005-08-21 17:17:40 -0700 removed attributes yield null rather than empty string 2022-08-02 08:18:29 -0700 1 1 1 Unclassified WebKit DOM 420+ Mac OS X 10.4 RESOLVED CONFIGURATION CHANGED P2 Normal --- 4565 1 darin webkit-unassigned ahmad.saleem792 andersca ap bfulgham cdumez curt.arnold ian rniwa vicki oldest_to_newest 17066 0 darin 2005-08-21 17:17:40 -0700 The W3C DOM test named hc_elementremoveattribute is failing because we return a JavaScript null rather than an empty string. This behavior makes sense and matches Firefox. Perhaps the test needs to be revised. 17725 1 darin 2005-08-26 19:54:33 -0700 Curt, what do you think? Is this a mistake in the test? 17726 2 darin 2005-08-26 19:54:40 -0700 Curt, what do you think? Is this a mistake in the test? 17731 3 curt.arnold 2005-08-26 20:32:56 -0700 This one is worth pushing up to the DOM IG. I haven't had time to do a full survey, but this seems to be one that the Java implementations pass and the ECMAScript implementations (IE, Mozilla and Safari) fail. The descriptions of getAttribute in DOM L1 Core and subsequent do not specify any conditions that getAttribute is allowed to return null and the conditions in the test satisify the criteria under which an empty string is specified as the return value. There would seem to be a reasonable case to support an errata allowing null as an acceptible return value and modify the test to accept either null or empty string. 25791 4 darin 2005-12-10 17:44:53 -0800 Some history. Originally we returned empty string in these cases. Then we had to change to be compatible with sites that assumed the behavior of Gecko (and presumably WinIE). So far the DOM committee does not seem sympathetic about the possibility of creating errata covering this. 66418 5 ian 2008-01-06 17:22:28 -0800 We should fix this in Web DOM Core. 1502889 6 lforschler 2019-02-06 09:03:01 -0800 Mass moving XML DOM bugs to the "DOM" Component. 1888360 7 ahmad.saleem792 2022-08-02 04:26:21 -0700 From the test case URL - https://www.w3.org/2007/03/dom-tests/hc_elementremoveattribute.html I am getting following behavior across browsers: > Firefox Nightly 105: Test: http://www.w3.org/2001/DOM-Test-Suite/level1/core/hc_elementremoveattribute Status: failure Detail: attrValue: assertEquals failed, actual null, expected . > Chrome Canary 106: Test: http://www.w3.org/2001/DOM-Test-Suite/level1/core/hc_elementremoveattribute Status: failure Detail: attrValue: assertEquals failed, actual null, expected . > Safari 15.6 on macOS 12.5 Test: http://www.w3.org/2001/DOM-Test-Suite/level1/core/hc_elementremoveattribute Status: failure Detail: attrValue: assertEquals failed, actual null, expected . __________ Since all browsers are matching, we can mark this as 'RESOLVED CONFIGURATION CHANGED". Thanks!