22292 - [UI] Javascript errors in create profile wizard

Status: VERIFIED FIXED

(SeaMonkey :: Startup & Profiles, defect, P2)

Description

[selmer (gone)]

build 1999122109
Here is the console message:

JavaScript Error: TypeError: prefix has no properties
URL:
chrome://global/content/widgetStateManager.js
LineNo: 271

This happens when I hit the Next button on the first page of CPW.  At least one
time, I did not get this error and actually progressed through the wizard.

Comment 1

[racham]

Adding UI tag to the summary line. Makes isolation of UI bugs easier.

Comment 2

[Ben Goodger (use ben at mozilla dot org for email)]

okay that's just weird. (I've said that before, too... ¬_¬)

my code looks okay.. it's passing in strings into the function where this error
occurs. the only reason I can think of where you wouldn't get this is that the
string tag is undefined (and hence with no length property). I can't understand
why this would be so though, I've never seen it and can't see it today's build.
please let me know if this continues.

Comment 3

[Grace Bush]

I am seeing this in build 1999122208 on Linux so far.  I can create one profile
per ProfileManager session. Subsequent attempts to create additional profiles
give me the error message noted above

Comment 4

[don]

M13 ...

Comment 5

[Ben Goodger (use ben at mozilla dot org for email)]

*** Bug 22557 has been marked as a duplicate of this bug. ***

Comment 6

[Ben Goodger (use ben at mozilla dot org for email)]

hm.. I wonder if this is some sort of back end regression. I have code in a
build from 12/10 that does not exhibit this problem, however when I copy the
profile chrome folder from that build into one from a couple of days ago it
shows the problem.

Comment 7

[Ben Goodger (use ben at mozilla dot org for email)]

push back until I can find a new owner for this... (supposedly its brutal
sharing)...

Comment 8

[(not reading, please use [e-mail] instead)]

I think waterson has a fix in his tree for a bunch of brutal sharing bugs (that
were previously mailnews bugs).

perhaps this should be re-assigned to him?

Comment 9

[Chris Waterson]

marking fixed: i'm not seeing these anymore after checking in a fix to 22915

Comment 10

[Grace Bush]

not seeing these either, rechecked on build 2000011313