6006 2005-12-08 03:57:59 -0800 document.getElementById does not behave in the same way as Internet Explorer (Win) 2019-02-06 09:02:47 -0800 1 1 1 Unclassified WebKit DOM 420+ Mac OS X 10.4 RESOLVED INVALID P2 Normal --- 1 andrew webkit-unassigned ap cdumez ian jason.hu rniwa zcorpan oldest_to_newest 25710 0 andrew 2005-12-08 03:57:59 -0800 In Internet Explorer, document.getElementById() in JavaScript will return form elements (input, select, etc) but not other elements (p, div, etc) with the same name as the id being requested (even if their id is different to the name). This causes some IE-specific JavaScript to fail on Safari as it (rightly according to the specifications) ignores the name when finding the elements requested. An affected product is the eService administration interface from Right Now software (http:// www.rightnow.com/eservice.html) although this interface does claim to only support IE 5.5+. A sample test case will be attached to this bug shortly. 25711 1 5000 andrew 2005-12-08 03:59:27 -0800 Created attachment 5000 Simple demonstration page 25713 2 andrew 2005-12-08 04:09:37 -0800 To clarify, when IE walks the tree looking for elements that match the document.getElementById() request, it returns the first element that matches: - id is equal to requested id - element is a form element, and its name matches the requested id 28692 3 gavin 2006-01-17 07:27:02 -0800 If any such broken behavior is introduced, it should be only exist in some alternative 'compliant' mode. IE is simply wrong, and steadily losing market share. Suggest you change this bug to invalid. (Some believe that 'de facto' standards present in other browsers are more important than the Standards themselves. I believe the opposite. Matching the spec instead of IE is not a 'bug'. I accept that there are people with both opinions; I do not know which opinion drives Safari's development team.) 60589 4 ap 2007-11-07 13:03:10 -0800 *** Bug 15127 has been marked as a duplicate of this bug. *** 60590 5 ap 2007-11-07 13:04:08 -0800 From bug 15127: Opera has this quirk, but is apparently going to remove it from their 9.50 release: "Removed IE-compatibility where Document.getElementById treated name and id attributes the same, which caused problems with jQuery." 62269 6 ap 2007-11-25 02:49:21 -0800 This causes major problems at the site of Beeline, a major mobile provider in Russia. Affected pages are only available to customers. 65419 7 anantha 2007-12-27 17:58:05 -0800 "http://markets.themarker.com/tmc/investorGuide.jhtml?layer=investorGuide" (a major Israeli finance portal also has this issue) 100396 8 zcorpan 2008-11-26 04:10:14 -0800 Is this still an issue? # [13:14] <zcorpan> it seems we have lots of bugs saying that getElementById works with name='' # [13:14] <zcorpan> which we dropped in 9.5 # [13:15] <zcorpan> and no bugs on it not working with name='', afaict # [13:15] <zcorpan> also, i think ie8 doesn't look at name='' (in ie8 mode) 1133791 9 rniwa 2015-10-16 00:58:22 -0700 This is no longer the case with newer versions of IE (e.g. IE9). 1502844 10 lforschler 2019-02-06 09:02:47 -0800 Mass moving XML DOM bugs to the "DOM" Component. 5000 2005-12-08 03:59:27 -0800 2005-12-08 03:59:27 -0800 Simple demonstration page test.html text/html 530 andrew PGh0bWw+CjxoZWFkPgo8dGl0bGU+QnJva2VuIGluIHRoYXQgSUUgV2F5PC90aXRsZT4KPC9oZWFk Pgo8Ym9keT4KPHA+CklmIHdlJ3JlIGJyb2tlbiBsaWtlIElFLCB0aGUgZm9sbG93aW5nIGZpZWxk IHdvdWxkIGNvbnRhaW4gIkJyb2tlbiBsaWtlIElFIi4KTm90ZSB0aGF0IGV2ZW4gdGhvdWdoIHRo ZSBpZCBkb2Vzbid0IG1hdGNoIHRoZSByZXF1ZXN0ZWQgaWQsIElFIHRoaW5rcyB0aGF0IGl0CmNh biBtYWtlIGl0IHVwIG9uIHRoZSBmbHkuIEN1dGUuCjwvcD4KPHA+ClZlcmlmaWVkIHRoaXMgaXMg YnJva2VuIG9uIElFIDYgU1AyCjwvcD4KPGlucHV0IHR5cGU9InRleHQiIG5hbWU9InRlc3RFbGVt ZW50IiBpZD0ic29tZXRoaW5nRWxzZSI+CjxzY3JpcHQgbGFuZ3VhZ2U9IkphdmFTY3JpcHQxLjEi IHR5cGU9InRleHQvamF2YXNjcmlwdCI+CnZhciBlbGVtOwplbGVtID0gZG9jdW1lbnQuZ2V0RWxl bWVudEJ5SWQoInRlc3RFbGVtZW50Iik7CmVsZW0udmFsdWUgPSAiQnJva2VuIGxpa2UgSUUiOwoK PC9zY3JpcHQ+CjwvYm9keT4=