173687 - JavaScript in Phoenix 0.2 different from Mozilla 1.2a

Status: VERIFIED INVALID

(Firefox :: General, defect)

Description

[Fini A. Alring]

I have over the last couple of days experienced many differences in Phoenix 0.2
and Mozilla 1.2a, while coding JavaScript and using DOM..

My last incident happened when putting the following in a html page:
	<div id="xmlDeposit01">
		<guiconfig id="myFirstTypes">
			<type-defs>
			<type name="str" />
			<type name="int" />
			<type name="date" />
			</type-defs>
			<sub-types/>
		</guiconfig>
	</div>

and trying to access it from JavaScript using:

alert(document.getElementById('xmlDeposit01').childNodes.length);

Phoenix 0.2 returns 1, and Mozilla 1.2a returns 2.

I have not had success with accessing the children of the DIV tag in Phoenix,
but have no trouble in Mozilla 1.2a. - I hope this helps more than it confuses,
otherwise please contact me and I will provide more help.

Regards Fini A. Alring

Comment 1

[Asa Dotzler [:asa]]

if this is different than the latest Mozilla build (1.2a is ancient) then it may
be a Phoenix bug. Have you tested the latest build?
http://komodo.mozilla.org/pub/mozilla/nightly/latest-trunk/

Comment 2

[Neil Cronin]

it looks to me like 1 is the correct return value.

Comment 3

[Fini A. Alring]

Neil: Yes, that wondered me too, but the reason I submitted this bug, is that I
feel it is disturbing that the functionality of Mozilla is differing form
Phoenix in so many ways that I had to change between browsers from Phoenix to
Mozilla in order to not get bugs in my application..
I will return with more info if the situation continues.

Comment 4

[Neil Cronin]

Fini, this is no doubt a bug in mozilla that has been fixed.  can you test a
recent version of mozilla?  if you get the same results you got with 1.2a, it
looks to me like you should file a bug on mozilla.

in any case, I don't see what the bug is here, since your code is working fine
on phoenix.

Comment 5

[Fini A. Alring]

Hi Neil: I think it is best that I do some more testing, and if I discover more
problems I will try to get the time to make a proper test-case, and report it in
bugzilla again. (I am doing some very complex api's for manipulating xml data,
and as such the bugs can be pretty hard to make into simple test cases,
especially  while on a tight deadline)  - Best Regards Fini A. Alring

Comment 6

[Neil Cronin]

recommend RESOLVED/INVALID since the initial report describes correct behaviour.

Comment 7

[Fini A. Alring]

let's do some more testing

Comment 8

[Simon Paquet [:sipaq]]

Mass-verifying of old bugs.