Simon Fraser [no longer active] Reporter
	Description • 23 years ago

Choosing 'View Saved Data' on the Edit menus results in the following:

JavaScript error: 
chrome://communicator/content/wallet/WalletViewer.js line 123: elementIDs has no
properties

and a window with blank right-hand panel. None of the form data can be viewed.

	Terri Preston
	Comment 1 • 23 years ago

What build are you using?

	Simon Fraser [no longer active] Reporter
	Comment 2 • 23 years ago

Using a current tip build. Saw on Mac and windows.

	Simon Fraser [no longer active] Reporter
	Comment 3 • 23 years ago

*** This bug has been marked as a duplicate of 64325 ***

	Stephen P. Morse
	Comment 4 • 23 years ago

We already know about this -- see bug 62730 for more details.

I'm going to close out that bug (rather than morph it) and keep this one as the 
tracking bug for this new symtptom.  cc'ing all people from that other bug 
report into this one.

	Stephen P. Morse
	Comment 5 • 23 years ago

No, this isn't a dup of bug 64325.  That's an old bug with different symptoms 
and a different cause.  I'm undupping these two reports.

	Stephen P. Morse
	Comment 6 • 23 years ago

I'm still waiting for ftang to respond to my question that was in bug 62730 
(which has now become this bug).  Namely:

   ftang, can you revise the patch to avoid this regression?

I'm referring to ftang's patch in bug 62730 which is the cause of the current 
problem.

	Stephen P. Morse
	Comment 7 • 23 years ago

To clarify, it's the 2001-05-30 14:28 from bug 62730 that I'm talking about.

	Stephen P. Morse
	Comment 8 • 23 years ago

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

	Jaime Rodriguez, Jr.
	Comment 9 • 23 years ago

Adding johng, tpringle and momoi to cc: list.

Marking as nsbeta1, nsCatFood, and nsDogFood.

	Stephen P. Morse
	Comment 10 • 23 years ago

reassigning to ftang at his request.

	Frank Tang
	Comment 11 • 23 years ago

It is totally my fault.

	Frank Tang
	Comment 12 • 23 years ago

mark it P1

	Frank Tang
	Comment 13 • 23 years ago

I suggest we back out 
http://bugzilla.mozilla.org/showattachment.cgi?attach_id=36541 to unblock QA

	Frank Tang
	Comment 14 • 23 years ago

I hate this!!! I cannot reproduce this problem in my local tree.... What is 
missing there ? I can reproduce this in nhotta's tree, but not my tree.....

	Charles Manske
	Comment 15 • 23 years ago

Do a complete clobber build -- that might help you to see it.

	Frank Tang
	Comment 16 • 23 years ago

ok. now I can reproduce this.

	Frank Tang
	Comment 17 • 23 years ago

steve mores and me agree that we should back out the last patch for now and find 
out what to do the right thing as the second step.

	Frank Tang
	Comment 19 • 23 years ago

I think I find a solution. See the patch. This fix the problem without backout 
the origional patch. 

	Frank Tang
	Comment 20 • 23 years ago

i back out the http://bugzilla.mozilla.org/showattachment.cgi?attach_id=36541 in 
the trunk after steve agree.

steve: can you review my new patch and try it in your tree/
I will on vacation tomorrow, if you have no problem with the patch, can you send 
to sr for me ?

	Stephen P. Morse
	Comment 21 • 23 years ago

Looks good to me.
r=morse

alecf, please sr

	Alec Flett
	Comment 22 • 23 years ago

I thought this got checked in yesterday? Anyway, sr=alecf

	Stephen P. Morse
	Comment 23 • 23 years ago

Alec: No, this didn't get checked in,  What happened yesterday was that the old 
checkin (which caused all the problems) got backed out.

	Stephen P. Morse
	Comment 24 • 23 years ago

All fixed now.  Yesterday ftang backed out his original patch which of course 
made this bug go away.  And after that he came up with what the patch should 
have been in the first place, and I just checked that in for him.

	Frank Tang
	Comment 25 • 23 years ago

break again. reopen

	Frank Tang
	Comment 26 • 23 years ago

remove morse' check in 6/15 since it break the 6/18 build.
now it really fix the problem 

	Terri Preston
	Comment 27 • 23 years ago

Still not fixed on Mac 2001061908

	Stephen P. Morse
	Comment 28 • 23 years ago

The fact that is suddenly broke again is a new bug.  See bug 86726.  Reclosing 
this one.

	Jens Lautenbacher
	Comment 29 • 23 years ago

And why is this new bug already closed again with reference to ftang's fixes?
I can only state that it still (20001061914, linux, modernskin) DOES NOT WORK.
The first panel (Name) comes up right, all other panels remain blank --- but
most panels will eventually appear when you resize the dialog. 
But even when they appear, The layout is broken when dropdown lists are used
(see attached screenshot of the creditcard panel es an example).
Basically the situation is not better than it was some weeks ago.

	Frank Tang
	Comment 31 • 23 years ago

morse check in the content package changes (the broken one) at Jun 7 17:54. 
9I finally fix the content package chagnes to the right state, as I believe, 
monday afternoon) Therefore, we should compare 6/7/2000 08000 build against 
200010619 mac and linux build. 
If they are the same, then it have nothing to do with the content package 
changes. 

	Frank Tang
	Comment 32 • 23 years ago

About Linux:
>And why is this new bug already closed again with reference to ftang's fixes?
>I can only state that it still (20001061914, linux, modernskin) DOES NOT WORK.
>The first panel (Name) comes up right, all other panels remain blank

I test linux 060613 build with ji@netscape.com . That build does not include the 
content package changes morse check in bug 62730. And it behave the same as 
above. Therefore, we can proff that the content package changes have no impact 
on the above behavior. It does not break it , neither fix it. 

	Frank Tang
	Comment 33 • 23 years ago

>I test linux 060613...
actually, I test 060613-branc (moz0.9.1) and moz0601-trunk build. both of them 
behave as today's linux build. which mean it is really a differnt bug- not 
caused by :
>JavaScript error: 
>chrome://communicator/content/wallet/WalletViewer.js line 123: elementIDs has 
no properties

	Jens Lautenbacher
	Comment 34 • 23 years ago

So which bug is the correct one to follow w.r.t the current situation? this one
here or bug 86726?

	Frank Tang
	Comment 35 • 23 years ago

mark this bug close. The current mac display problem is a seperate cause, exist 
in beta1 and have no relationship from the content package seperate work- I 
reopen 86726. The current linux display problme is a sepertae bug , exist in 
beta1 and have no relationship from the content package seperate work- Please 
file seperate bug against morse for it. 

close this bug since the origional report cause is gone and my duty of moving 
those file to US.jar is finish and done. 

	Frank Tang
	Comment 36 • 23 years ago

86276 is for mac. I am not sure it is the problem for linux or not. Maybe you 
should open a new bug for linux. But THIS 85300 is about "JavaScript error: 
chrome://communicator/content/wallet/WalletViewer.js line 123: elementIDs has no
properties" and no longer exist. 

	Terri Preston
	Comment 37 • 23 years ago

Verified javascript error fixed:
W2k build 2001062004
mac build 2001062005
linux build 2001062008

	Peter Jeziorek
	Comment 38 • 23 years ago

I'm still seeing this on the branch Linux build 2001062506. This first forms are
displayed. Click on address, phone numbers or anything else and the forms
disappear, even if saved information is present. There is no javascript error,
though.

	Stephen P. Morse
	Comment 39 • 23 years ago

This bug has been fixed.  What you are now reporting is a different bug -- 
namely 86726.

	Terri Preston
	Comment 40 • 23 years ago

Verified fixed, this bug is only for the javascript error and that has been 
fixed