Bug 4493 – add qualifiedName checking for empty string

• Component: DOM
• Status: RESOLVED FIXED

[Darin Adler]

[Darin Adler]

Created attachment 3438 [details]
adds code that knows that an empty qualified name is not valid

[Darin Adler]

Comment on attachment 3438 [details]
adds code that knows that an empty qualified name is not valid

Adele and Maciej are looking into this. The DOM specification clearly doesn't
call for INVALID_CHARACTER_ERR in the case of an empty string, so we're trying
to learn more about the conference call where someone decided this was correct
behavior.

[Darin Adler]

This bug affects these tests:

        dom/html/level2/core/createDocument08.html
        dom/html/level2/core/createDocumentType04.html

[Darin Adler]

Looks like this is definitely correct for DOM Level 3 and arguably OK for Level 2, so we're going to make 
the change.

[Maciej Stachowiak]

This behavior not even arguably ok for level 2, barring a possible future change to the level 2 spec. It 
likely doesn't matter for any real-world cases, but it seems silly to make a change for a test that isn't 
testing what it says it is.

[Darin Adler]

OK. Maciej, you're welcome to change this back, or resolve the problem in whatever other way you see fit. 
Since I didn't get any comment from you on this for a couple of weeks, I mistakenly thought you agreed 
with Curt that this should just be changed in our code.

[Lucas Forschler]

Mass moving XML DOM bugs to the "DOM" Component.