129776 - parseFromString not working on SVG Windows Nightlies

Status: RESOLVED WORKSFORME

(Core :: XML, enhancement)

Description

[Eric Murphy]

parseFromString seems to be dying. This is on 0.9.9 trunk builds (I have not
tested non-trunk yet).

I need this fixed for 0.9.9 for a whiteboard application that uses this.

Comment 1

[Eric Murphy]

Attachment: parse.html

It dies. alert doesn't show.

Comment 2

[Eric Murphy]

Ok, doesn't work in regular nightlies either.

Comment 3

[Eric Murphy]

Seems to depend on 92377 being fixed. The testcase no longer works after the 3rd.

Comment 4

[Peter Van der Beken [:peterv]]

WFM in both my Mac trunk build and in a Mac 0.9.9 nightly downloaded from
ftp.mozilla.org (2002030805). Any messages in the JS console? Try a new profile
and/or deleting the component registry and xpti.dat.

Comment 5

[Peter Van der Beken [:peterv]]

Removing the bogus dependency, bug 92377 has already been fixed. It might have
caused this but there's no dependency.

Comment 6

[Eric Murphy]

OK, after more extensive testing, I figured out this only affects SVG Windows
builds. It says "parseFromString is not a fuction". This is very weird. Works
fine on Linux SVG builds.

Comment 7

[Peter Van der Beken [:peterv]]

Attachment: DOM category dump

Comment 8

[Peter Van der Beken [:peterv]]

Could you save attachment 73444 [details] locally and open it, and tell us if DOMParser is
in the "JavaScript global constructor" list or in the "JavaScript DOM class"
list? Also, did you try deleting your component registry and the xpti.dat files?

Comment 9

[Eric Murphy]

It's in "JavaScript DOM class".

When I delete component.reg, then it works.

I tried the attachment again after deleting it, and it's still in the
"JavaScript DOM class".

Comment 10

[Heikki Toivonen (remove -bugzilla when emailing directly)]

I'll close this as INVALID because it gets fixed by deleting component.reg.

Comment 11

[Eric Murphy]

No. This is still a bug. Every new build I download, this has to be done. There
is something wrong.

Comment 12

[Eric Murphy]

Also, this problem started happening immediately after 92377 path was checked
in. This is no coincidence either.

Comment 13

[Peter Van der Beken [:peterv]]

I can't reproduce.

Comment 14

[Heikki Toivonen (remove -bugzilla when emailing directly)]

The fix to bug 92377 invalidated component.reg. That file simply needs to be
deleted and it will be recreated. We will not fix this by coding... (unless we
had a situation with duplicate UUIDs, which I doubt).

If nightly builds contain invalid component.reg, they should be cleaned by hand.
This of course does not need to be done for clobber builds (I assumed all
nightly builds were clobber builds). Adding leaf to Cc. Hmm... where do you
download SVG enabled builds (if not mozilla.org)? You should inform them to
clobber their build once.

Comment 15

[Eric Murphy]

There are nightly SVG builds on Mozilla.org. What is a clobber build?

Comment 16

[Heikki Toivonen (remove -bugzilla when emailing directly)]

clobber is a term we use in the make process which deletes all the old crap in
the tree so that next time you build you start from the beginning. 

Depend build is a build where you only build stuff that changed since the last
build.

Comment 17

[Heikki Toivonen (remove -bugzilla when emailing directly)]

Giving to leaf since this looks like it is some kind of
packaging/installer/zip/whatever problem.

Comment 18

[Jon Granrose]

no idea what an SVG build is, this bug needs to be assigned to whoever is doing
those builds.

Comment 19

[Eric Murphy]

Latest nightly builds work.