Closed
Bug 51059
Opened 26 years ago
Closed 26 years ago
Name field does not gain focus in login dialog
Categories
(Core :: DOM: UI Events & Focus Handling, defect, P3)
Tracking
()
VERIFIED
WORKSFORME
People
(Reporter: hcaley, Assigned: joki)
References
()
Details
(Keywords: helpwanted, Whiteboard: [nsbeta3-])
When going to a site that uses http auth the login box comes up and the name
field is highlighted, but the user can't type in a name. If the user then tabs
until the name box is highlighted again, he can then type in it.
Build ID 2000090106; been the same for the last few nightlies that I have tried
Comment 2•26 years ago
|
||
this link is inaccessible. please provide a URL that we can test. thanks.
Try https://internal.lumeria.com, or any site that uses auth
Comment 4•26 years ago
|
||
confirm on win2k with build from tip 9/1 at:
http://demo3.beatnik.com/qa/netscape
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Comment 5•26 years ago
|
||
updating summary and URL to reflect https:// issue.
Summary: When logging in with http, the name cannot be typed even though it is highlighted → When logging in with https, the name cannot be typed even though it is highlighted
Comment 6•26 years ago
|
||
updating summary again. over to networking. this is not https: specific.
Reporter, please see the bug writing guidelines at
http://www.mozilla.org/quality/bug-writing-guidelines.html to see the kind of
information we need to efficiently process your issue.
The workaround is to select the password field first then the name field.
Assignee: asa → gagan
Component: Browser-General → Networking
QA Contact: doronr → tever
Summary: When logging in with https, the name cannot be typed even though it is highlighted → Name field does not gain focus in login dialog
Comment 7•26 years ago
|
||
sorry. event handling.
Assignee: gagan → joki
Component: Networking → Event Handling
QA Contact: tever → janc
Simple workarounds exist, therefore:
This bug has been marked "future" because the original netscape engineer working
on this is over-burdened. If you feel this is an error, that you or another
known resource will be working on this bug,or if it blocks your work in some way
-- please attach your concern to the bug for reconsideration.
Target Milestone: --- → Future
My thoughts on the timeline would be, how often do users go to sites that use
authentication? Pretty often, I think, and every time they do this issue will
come up and make the browser look buggy. It seems like a simple thing to fix
too, from my point of view as a non-programmer ;)
Hmm, this is perhaps more common than I thought, but nowadays I believe the
really important sites in fact use secure connections and ask for the login &
password in an HTML page, not with the login dialog.
I am hoping this one would have a simple fix. Nominating for nsbeta3 because
every user that will face login dialogs is going to notice...
Keywords: correctness,
nsbeta3
Target Milestone: Future → ---
Ahem, every W3C member that tries to access W3C member-only pages would be
affected by this. We wouldn't want to alienate W3C members from Netscape, now
would we...
Comment 12•26 years ago
|
||
Marking nsbeta3-. It would be nice if somebody could modify the XUL to make
this work. Marking helpwanted also.
Keywords: helpwanted
Whiteboard: [nsbeta3-]
| Reporter | ||
Comment 13•26 years ago
|
||
Today's build seems to have fixed this problem...Build ID: 2000091408 on Linux
glibc2.1. However, actually submitting my auth with the Enter key crashes Mozilla.
| Assignee | ||
Comment 14•26 years ago
|
||
There was a lot of instability added near nsbeta3. Let's give this another day
then retest.
Status: NEW → ASSIGNED
This is working for me now, NT PR3 & Linux debug branch build from yesterday.
Marking worksforme.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → WORKSFORME
Comment 17•25 years ago
|
||
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
Updated•7 years ago
|
Component: Event Handling → User events and focus handling
You need to log in
before you can comment on or make changes to this bug.
Description
•