Closed
Bug 18444
Opened 25 years ago
Closed 25 years ago
[FEATURE]Titledbuttons need to be focusable
Categories
(Core :: XUL, defect, P3)
Tracking
()
VERIFIED
FIXED
M14
People
(Reporter: xiaotong, Assigned: hyatt)
References
Details
(Whiteboard: Fix in hand. Needs review from joki.)
In dialog (e.g. Open Web location), using Tab key does not loop through
all the controls, it does not go to OK and Cancel buttons. There is no way
to reach OK and Cancel by using keyboard.
Updated•25 years ago
|
Assignee: shuang → trudelle
Component: UE/UI → XP Toolkit/Widgets
Comment 1•25 years ago
|
||
Looks like peter may have better sense about this...
Updated•25 years ago
|
Assignee: trudelle → sdagley
Target Milestone: M13
Comment 2•25 years ago
|
||
reassigning to sdagley as p3 for m13
Updated•25 years ago
|
Status: NEW → ASSIGNED
Comment 3•25 years ago
|
||
Forgot to cc: hangas on this one in case it's related to the dialog overlay that
provides for the specialized behavior in ok/cancel buttons
Updated•25 years ago
|
Summary: Tab key in dialog does not go to OK & Cancel buttons → [FEATURE]Tab key in dialog does not go to OK & Cancel buttons
Comment 4•25 years ago
|
||
featuring
Updated•25 years ago
|
Assignee: sdagley → hyatt
Status: ASSIGNED → NEW
Comment 5•25 years ago
|
||
hyatt has been thwacking on tabbing code and said to re-assign tabbing bugs to
him
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Summary: [FEATURE]Tab key in dialog does not go to OK & Cancel buttons → [FEATURE]Titledbuttons need to be focusable
Assignee | ||
Updated•25 years ago
|
Target Milestone: M13 → M14
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 6•25 years ago
|
||
Fixed, although titledbuttons with user-focus: ignore arent' smart enough
to ignore the tabbing. This is true of HTML elements as well.
Comment 7•25 years ago
|
||
hyatt, is this supposed to be in the 2000011308 build?
Updated•25 years ago
|
Status: RESOLVED → REOPENED
Comment 8•25 years ago
|
||
well no matter, cuz with the 2000011408 comm opt builds this ain't fixed.
If i select File| Open web location then click in the text field or the checkbox
and hten try to tab over nothing happens except...
OH MY GOD!
is printed to the console for each tab press.
Assignee | ||
Updated•25 years ago
|
Status: REOPENED → ASSIGNED
Assignee | ||
Updated•25 years ago
|
Resolution: FIXED → ---
Assignee | ||
Comment 9•25 years ago
|
||
You're right. Thanks for pointing out the error message. Led me right to the
problem. joki, I'd like you to review this little patch to
GetNextTabbableContent. I set hidden to PR_TRUE if I can't find a primary frame
for the content that might be tabbed into. This keeps us from tabbing into
focusable content that has no associated frame (e.g., because of display: none).
With your approval, I'll check this puppy in when M14 opens.
The following code is inserted right after the if/else statements for all the
form elements+trees+titledbuttons in GetNextTabbableContent.
// Get the primary frame for the widget. We don't tab into anything
// that doesn't have a frame.
nsCOMPtr<nsIPresShell> shell;
if (mPresContext) {
nsresult rv = mPresContext->GetShell(getter_AddRefs(shell));
if (NS_SUCCEEDED(rv) && shell){
nsIFrame* potentialFrame;
shell->GetPrimaryFrameFor(child, &potentialFrame);
if (!potentialFrame)
hidden = PR_TRUE;
}
}
Whiteboard: Fix in hand. Needs review from joki.
Assignee | ||
Comment 10•25 years ago
|
||
Fixed.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
Comment 11•25 years ago
|
||
was this fix part of your changes from last night (1/24) that are/were being backed out?
Comment 12•25 years ago
|
||
this is VERIFIED on all platforms with the 2000020108 builds but I just wrote bug 26342 to address the fact that there is no visual
indication of which widget has focus.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•