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)

defect

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.
Adding crash keyword
Keywords: crash
can you specify which build you are using?
Severity: normal → major
Status: UNCONFIRMED → NEW
Ever confirmed: true
QA Contact: lchiang → esther
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
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
Putting on [nsbeta2+][6/15] to fix crash
Whiteboard: [nsbeta2+][6/15]
Target Milestone: M16 → M19
Status: NEW → ASSIGNED
Whiteboard: [nsbeta2+][6/15] → [nsbeta2+][6/15] need eric's help
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.
New bug logged for tabbing problem when getting to check box 43309.
*** Bug 43985 has been marked as a duplicate of this bug. ***
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
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
removing nsbeta3 keyword
Keywords: nsbeta3
Tabbing/accessiblity, targeting Mozilla 0.9
Target Milestone: Future → mozilla0.9
Changing qa assign to myself.
QA Contact: esther → pmock
Summary: Shifted Tab partially broken in address book name field → [access]Shifted Tab partially broken in address book name field
-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
Status: NEW → ASSIGNED
accessibility bugs -> P1.
Priority: P2 → P1
OS: Linux → All
Hardware: PC → All
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
Assign it to myself..
QA Contact: pmock → fenella
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
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.