8310 - Severe Javascript errors using Netscape Messenger Express

Status: VERIFIED WORKSFORME

(Core :: DOM: UI Events & Focus Handling, defect, P1)

Description

[richmond]

Messenger express is an e-mail client written completely in Javascript. It
works on IE >= 3 and Navigator >= 3.01, but fails to even login with any
version of mozilla over the past several months. This app probably stresses
Javascript functionality more than anything else on the net.

The login page has some simple Javascript to deal with form submission and
password clearing. Basic tab and return keys fail to work on this page but
mouse manipulation can execute a post to "login.msc". This is supposed to
return an HTTP redirect to "en/mail.html" that is a frameset with 4 invisible
frames for data and one for the UI. This does not work and I get a blank screen
instead. As the initial frameset loads, the screen should show "loading please
wait". Invisible frames should then be loaded with javascript objects from
Netscape's messaging server(via onLoad() handler) and the UI is then completely
constructed with client-side JS. No UI elements are designed on the server.

msg54.mcom.com is an internal Netscape server. One external site is
www.olemail.com(spanish), and let me know if you need another site for testing.

Comment 1

[leger]

Moving to Javascript Engine component.
richmond...Javascript component is being retired shortly.  Please use Javascript
Engine for JS component bugs.

cbegle, is this for your folks?

Comment 2

[cbegle]

this is event stuff.

Comment 3

[richmond]

Setting priority(forgot to do it at first?). ME has sold several multi-million
seat deals to Europe and Canada that are now deploying so this will be a
popular problem. I will file separate bugs once basic login and startup works.

Comment 4

[skliaroukp]

<SELECT NAME="language_select" SIZE="1"
ONCHANGE="window.open(this.options[this.selectedIndex].value,'_top');
language_select.options[0].selected=true">

shows
JavaScript error: language_select is not defined

Comment 5

[richmond]

The comment from [e-mail] is nonsensical and must apply to some
other bug

Comment 6

[richmond]

Making more progress. Location.search is not updated on HTTP redirects and
location.replace() is broken in viewer.exe

Comment 7

[John G. Myers]

Still cannot log in.  [e-mail] is investigating.

Comment 8

[ekrock's old account (dead)]

Removing TESTCASE from Status as there is no test case attached. If none is
needed, mark [DONTTEST]. (please always use brackets--thanks!)

Comment 9

[John G. Myers]

Login is now working with M12, but logout is broken:

JavaScript Error: TypeError: this.hdl.close is not a function

Folks within Netscape can try it out against vadar.mcom.com, userid "x" password
"x".

Comment 10

[John G. Myers]

Also, the tab key is not working for moving the cursor from the "username" field
to the "Password" field, and the enter key is not working for submitting the
form.

Comment 11

[Jan Carpenter]

marking beta1

Comment 12

[John G. Myers]

Marking 4xp.

Comment 13

[Kevin McCluskey (gone)]

I can login with todays build.

The tab key now moving the cursor from the "username" field to the "Password" 
field, and the enter key is now working for submitting the form.

The page does not load however. After submitting the form the page goes blank, 
this sounds like it will be addressed by bug 9472 that this bug depends on.

Comment 14

[Kevin McCluskey (gone)]

Setting m17 milestone

Comment 15

[John G. Myers]

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

Comment 16

[Jan Carpenter]

adding beta2 keyword, and removing pdt status

Comment 17

[Paul MacQuiddy]

removing beta1 keyword so it doesn't show up on beta1 radar

Comment 18

[leger]

richmond, 384993 was fixed on 04/03.  Can you check to see if this is still an 
open bug for you?  Thanks!

Comment 19

[John G. Myers]

We can't retest until the lab move to Santa Clara is complete.  I should 
hopefully be able to test this by the end of next week.

Comment 20

[leger]

Putting on [nsbeta2-] radar. Not critical to beta2, gagan expects a fix soon 
anyway.

Comment 21

[John G. Myers]

This seems to be working now, modulo the unqualified-domain issue covered by 
bug 39386

To test, try we-gotmail.red.iplanet.com:80 with userid mozilla1 password 
mozilla1. (only accessable from Netscape and Iplanet).

Comment 22

[Jan Carpenter]

Can't test.
I went to the site we-gotmail.red.iplanet.com:80 and used the login/password of 
mozilla1 and get "Invalid username or password"

Is there some other way to test this?

Comment 23

[John G. Myers]

Argh, they keep nuking the test accounts.  Will get them recreated.

Comment 24

[Jan Carpenter]

Crashed Win98 
2000-06-28-21-M17
Talkback report:  13367340

Comment 25

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

Can you please see if this is working properly now, what problems remain? I can
log in and a 20 sec fooling around did not crash the browser nor did I find
anything that does not work. Hmm, seems like there is still bug 27048 that this
depends on, but didn't check what this affects.

Comment 26

[ckritzer (gone)]

Mass update:  changing qacontact to [e-mail]

Comment 27

[ekrock's old account (dead)]

Haven't tested myself, but per above comments, marking WORKSFORME. Adding
verifyme keyword--verifiers please pound on this and make sure the problem is
really, truly gone. Thanks!

Also nominating nsbeta3 for correctness because if the problem *isn't* fixed,
it's an nsbeta3 stopper as it blocks usage of Messenger Express.

Comment 28

[Loco]

Updating QA Contact.

Comment 29

[Hixie (not reading bugmail)]

Reassigning QA Contact for all open and unverified bugs previously under Lorca's
care to Gerardo as per phone conversation this morning.

Comment 30

[Madhur Bhatia]

QA contact updated

Comment 31

[luis rincon]

verified on build 2001-07-11-trunk