Closed
Bug 301318
Opened 19 years ago
Closed 19 years ago
Initial focus in help
Categories
(SeaMonkey :: Help Viewer, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: aaronlev, Assigned: aaronlev)
References
Details
(Keywords: access)
Attachments
(1 file)
|
1.03 KB,
patch
|
mconnor
:
approval1.8b4+
|
Details | Diff | Splinter Review |
Currently the initial focus goes to the content pane. The only problem with this is that as a screen reader user, one will typically use tab to go through all the elements in a dialog to see what is there. When you tab through you just see links. This will usually lead to the impression that the content pane is all that there is in the dialog. I recommend starting initial focus in the first field -- quick search. This is a more useful place anyway. I'm not generally going to be reading "welcome to deer park alpha 2". Maybe once.
Updated•19 years ago
|
Component: Help Documentation → Help Viewer
Product: Firefox → Toolkit
QA Contact: help.documentation → help
| Assignee | ||
Comment 1•19 years ago
|
||
Mike, can you comment on whether it is okay with you to change this?
Blocks: deera11y
| Assignee | ||
Comment 3•19 years ago
|
||
| Assignee | ||
Updated•19 years ago
|
Attachment #189855 -
Flags: first-review?(mconnor)
Comment 4•19 years ago
|
||
Comment on attachment 189855 [details] [diff] [review] Set initial after first content loads because loading the content resets the focus >? q.bat >? content/q >Index: content/help.js >=================================================================== >RCS file: /cvsroot/mozilla/toolkit/components/help/content/help.js,v >retrieving revision 1.33 >diff -p -u -5 -r1.33 help.js >--- content/help.js 7 Jul 2005 19:30:09 -0000 1.33 >+++ content/help.js 20 Jul 2005 02:07:54 -0000 >@@ -527,10 +528,13 @@ nsHelpStatusHandler.prototype = { > this.throbberElement.setAttribute("busy", "true"); > } else if (aStateFlags & nsIWebProgressListener.STATE_STOP) { > if (aRequest && this.throbberElement) { > this.throbberElement.removeAttribute("busy"); > } >+ if (!document.commandDispatcher.focusedElement) { >+ focusSearch(); // no focus in window yet, so set initial focus to search field >+ } r+a=me, but it'd be great if you could remove the previous if block, and basically all of the references to this.throbberElement ;) If not, please just file a follow on me to clean that up.
Attachment #189855 -
Flags: first-review?(mconnor)
Attachment #189855 -
Flags: first-review+
Attachment #189855 -
Flags: approval1.8b4+
| Assignee | ||
Comment 5•19 years ago
|
||
Checking in content/help.js; /cvsroot/mozilla/toolkit/components/help/content/help.js,v <-- help.js new revision: 1.34; previous revision: 1.33 done
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Aaron, what's with all the removed code in the patch you checked in? http://bonsai.mozilla.org/cvsview2.cgi?diff_mode=context&whitespace_mode=show&subdir=mozilla/toolkit/components/help/content&command=DIFF_FRAMESET&file=help.js&rev1=1.33&rev2=1.34&root=/cvsroot The patch you posted here only adds 3 lines, the patch that was checked in (judging from that cvs diff) removes all kinds of stuff, and probably broke the back/forward buttons in the help viewer!
Oh, I didn't notice comment 4. Anyway, I think that the code you removed caused bug 302111.
Updated•9 years ago
|
Product: Toolkit → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•