Closed Bug 6552 Opened 25 years ago Closed 25 years ago

Browser-generated forms not triggering single-signon

Categories

(SeaMonkey :: Passwords & Permissions, defect, P3)

Product:
SeaMonkey
Component:
Passwords & Permissions
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 18565

People

(Reporter: paulmac, Assigned: morse)

Details

Browser-generated forms are not triggering single-signon on all platforms using
5/14 builds. This is due to the unavailability of modal dialogues, which are due
with necko.

This bug is a reminder to test browser-generated forms when modal dialogues are
available - http://www.roamers.com/users/paulmac is a good test

Will mark for M7, when the first landing of necko is scheduled.
Target Milestone: M8
Status: NEW → ASSIGNED
Target Milestone: M10 → M11
who should get this?
who should get this?
ah, I had forgotten about this. Steve, do you know the status of this?
Assignee: paulmac → morse
Status: ASSIGNED → NEW
I'll take it.  davedm and I have been working on it.
Status: NEW → ASSIGNED
Blocks: 18471
This is now working for http authentication and for ftp authentication.  Still
needs to be done for mail/news and for composer.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Looks like composer publishing (which is the part of composer that does
authentication) will not be in 5.0 according to cmanske.

The only remaining browser-generated authentication form that still needs single
signon is in mail/news.  Phil Peterson opened up bug 18565 on that.  So I'm
marking this bug as a dup, and future tracking of this feature can be done in
the new bug report.

*** This bug has been marked as a duplicate of 18565 ***
Status: RESOLVED → VERIFIED
[bugday] read both and i'm verifying that they're the same.
No longer blocks: 18471
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.