Closed
Bug 38895
Opened 25 years ago
Closed 24 years ago
Shifted Tab partially broken in address book name field
Categories
(SeaMonkey :: MailNews: Address Book & Contacts, defect, P1)
SeaMonkey
MailNews: Address Book & Contacts
Tracking
(Not tracked)
VERIFIED
WORKSFORME
mozilla0.9
People
(Reporter: mrroper1, Assigned: bryner)
References
Details
(Keywords: access, crash, Whiteboard: [nsbeta2-] need eric's help)
When you hit shift+tab while making an address book entry it crashes the whole
thing. Also if you mouse to something you already typed it sometimes looses the
cursor.
can you specify which build you are using?
Severity: normal → major
Status: UNCONFIRMED → NEW
Ever confirmed: true
QA Contact: lchiang → esther
Comment 3•25 years ago
|
||
I don't crash, but I do get into an infinite loop. It also happens on Windows.
The infinite loop occurs in nsEventStateManager::GetNextTabbableContent.
The way I reproduce this is to go to the address book.
Choose new card.
Tab into the Work: field.
Then hit shift-tab.
At this point there's an infinite loop.
I'm reassigning to trudelle because I think this is an XPToolkit bug.
Assignee: putterman → trudelle
Comment 4•25 years ago
|
||
bumping severity to critical, nominating nsbeta2, reassigning to saari as p2 for
m16. This bug applies only to the original described defect, everything after
the 'also' should be in a separate bug report.
Assignee: trudelle → saari
Severity: major → critical
Keywords: nsbeta2
Priority: P3 → P2
Target Milestone: --- → M16
Updated•25 years ago
|
Target Milestone: M16 → M19
Updated•24 years ago
|
Status: NEW → ASSIGNED
Whiteboard: [nsbeta2+][6/15] → [nsbeta2+][6/15] need eric's help
Comment 6•24 years ago
|
||
Cleaning up status whiteboard by marking beta2 minus (6/15 has passed)
Whiteboard: [nsbeta2+][6/15] need eric's help → [nsbeta2-] need eric's help
Using build 2000-06020 on win98, mac and linux shift+tab doesn't hang up the
card, app or system. I don't crash either. Shift+tab within a group on the
Name tab will move up one field so it partially works. Shift+tab won't move up
from the Phone group to the Internet group. I will log new bug for this. This
can be resolved as originally stated, but not sure if it was specifically fixed
or not so not sure what the resolution should be.
Note: this test only applys to using the Name tab, once a user moves to another
tab there are other problems which are covered in bug 38358.
Comment 10•24 years ago
|
||
updated summary, ->Future, normal severity. I think we'll have to live with this.
Severity: critical → normal
Summary: Shifted Tab crashed address book → Shifted Tab partially broken in address book name field
Target Milestone: M19 → Future
Comment 11•24 years ago
|
||
There is soemthing very wrong with the parent/child frame hierarchy which is
causing this bug, so it should really be investigated further in beta3
Keywords: nsbeta3
Comment 13•24 years ago
|
||
Tabbing/accessiblity, targeting Mozilla 0.9
Target Milestone: Future → mozilla0.9
Updated•24 years ago
|
Summary: Shifted Tab partially broken in address book name field → [access]Shifted Tab partially broken in address book name field
Comment 15•24 years ago
|
||
-bryner, access->keyword. Brian - Chris is swamped, could you take this on?
Assignee: saari → bryner
Status: ASSIGNED → NEW
Keywords: access
Summary: [access]Shifted Tab partially broken in address book name field → Shifted Tab partially broken in address book name field
Assignee | ||
Updated•24 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Updated•24 years ago
|
OS: Linux → All
Hardware: PC → All
Assignee | ||
Comment 17•24 years ago
|
||
Using a current build on Linux, I can successfully tab through (both forward and
backwards) every field. Marking WORKSFORME, please reopen if I'm missing something.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Comment 19•24 years ago
|
||
Linux (2001-02-20-12 mtrunk)
Win32 (2001-02-20-09 mtrunk)
Mac (2001-02-20-12 mtrunk)
This problem is fixed.
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•