Closed Bug 8310 Opened 21 years ago Closed 20 years ago
Assignee: leger → mccabe
QA Contact: leger → cbegle
this is event stuff.
Assignee: mccabe → joki
QA Contact: gerardok → janc
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.
The comment from email@example.com is nonsensical and must apply to some other bug
Making more progress. Location.search is not updated on HTTP redirects and location.replace() is broken in viewer.exe
Still cannot log in. firstname.lastname@example.org is investigating.
Removing TESTCASE from Status as there is no test case attached. If none is needed, mark [DONTTEST]. (please always use brackets--thanks!)
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.
Whiteboard: [PDT-] → [PDT-] waiting for iPlanet to deploy fix to 384993
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.
Setting m17 milestone
Target Milestone: M17
*** Bug 32631 has been marked as a duplicate of this bug. ***
adding beta2 keyword, and removing pdt status
Whiteboard: [PDT-] waiting for iPlanet to deploy fix to 384993 → waiting for iPlanet to deploy fix to 384993
removing beta1 keyword so it doesn't show up on beta1 radar
richmond, 384993 was fixed on 04/03. Can you check to see if this is still an open bug for you? Thanks!
Whiteboard: waiting for iPlanet to deploy fix to 384993 → [NEED INFO]waiting for iPlanet to deploy fix to 384993
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.
Putting on [nsbeta2-] radar. Not critical to beta2, gagan expects a fix soon anyway.
Whiteboard: [NEED INFO]waiting for iPlanet to deploy fix to 384993 → [nsbeta2-]waiting for iPlanet to deploy fix to 384993
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).
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Whiteboard: [nsbeta2-]waiting for iPlanet to deploy fix to 384993 → [nsbeta2-]
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?
Argh, they keep nuking the test accounts. Will get them recreated.
Whiteboard: [nsbeta2-] → [nsbeta2-] Awaiting recreation of site...
Crashed Win98 2000-06-28-21-M17 Talkback report: 13367340
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
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.
Mass update: changing qacontact to email@example.com
QA Contact: janc → ckritzer
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.
Updating QA Contact.
QA Contact: ckritzer → lorca
Reassigning QA Contact for all open and unverified bugs previously under Lorca's care to Gerardo as per phone conversation this morning.
QA Contact: lorca → gerardok
QA contact updated
QA Contact: gerardok → madhur
verified on build 2001-07-11-trunk
Status: RESOLVED → VERIFIED
Component: Event Handling → User events and focus handling
You need to log in before you can comment on or make changes to this bug.