Closed
Bug 802415
Opened 13 years ago
Closed 13 years ago
[AccessFu] Introduce better feedback when switching tabs and focusing on content area.
Categories
(Core :: Disability Access APIs, defect)
Core
Disability Access APIs
Tracking
()
VERIFIED
FIXED
mozilla19
People
(Reporter: eeejay, Assigned: eeejay)
References
Details
Attachments
(1 file)
No description provided.
Assignee | ||
Comment 1•13 years ago
|
||
Attachment #672086 -
Flags: review?(dbolter)
![]() |
||
Comment 2•13 years ago
|
||
Comment on attachment 672086 [details] [diff] [review]
Report virtual cursor position on selected tab when tab changes, or when focus moves to content area.
Review of attachment 672086 [details] [diff] [review]:
-----------------------------------------------------------------
::: accessible/src/jsat/AccessFu.jsm
@@ +198,5 @@
> + this._focused = JSON.parse(aData);
> + if (this._focused) {
> + let mm = Utils.getMessageManager(Utils.getCurrentBrowser(this.chromeWin));
> + mm.sendAsyncMessage('AccessFu:VirtualCursor',
> + {action: 'whereIsIt', move: true});
What is the 'move' for?
@@ +236,5 @@
> + {
> + if (this._focused) {
> + let mm = Utils.getMessageManager(Utils.getCurrentBrowser(this.chromeWin));
> + // We delay this for half a second so the awesomebar could close,
> + // and we could use the current coordinates for the content item.
Blarg. How about adding a comment:
// XXX TODO figure out how to avoid magic wait here.
::: accessible/src/jsat/content-script.js
@@ +53,5 @@
> break;
> case 'moveToPoint':
> moved = vc.moveToPoint(rule, details.x, details.y, true);
> break;
> + case 'whereIsIt':
This grew on me (another option might be 'whereAreYou').
@@ +55,5 @@
> moved = vc.moveToPoint(rule, details.x, details.y, true);
> break;
> + case 'whereIsIt':
> + if (!forwardMessage(vc, aMessage)) {
> + if (!vc.position && aMessage.json.move)
Why do you check move?
Assignee | ||
Comment 3•13 years ago
|
||
(In reply to David Bolter [:davidb] from comment #2)
> Comment on attachment 672086 [details] [diff] [review]
> Report virtual cursor position on selected tab when tab changes, or when
> focus moves to content area.
>
> Review of attachment 672086 [details] [diff] [review]:
> -----------------------------------------------------------------
>
> ::: accessible/src/jsat/AccessFu.jsm
> @@ +198,5 @@
> > + this._focused = JSON.parse(aData);
> > + if (this._focused) {
> > + let mm = Utils.getMessageManager(Utils.getCurrentBrowser(this.chromeWin));
> > + mm.sendAsyncMessage('AccessFu:VirtualCursor',
> > + {action: 'whereIsIt', move: true});
>
> What is the 'move' for?
>
If the virtual cursor is not any anything, move it to the first object in the docu using the Simple rule.
> @@ +236,5 @@
> > + {
> > + if (this._focused) {
> > + let mm = Utils.getMessageManager(Utils.getCurrentBrowser(this.chromeWin));
> > + // We delay this for half a second so the awesomebar could close,
> > + // and we could use the current coordinates for the content item.
>
> Blarg. How about adding a comment:
> // XXX TODO figure out how to avoid magic wait here.
>
Sure thing.
> ::: accessible/src/jsat/content-script.js
> @@ +53,5 @@
> > break;
> > case 'moveToPoint':
> > moved = vc.moveToPoint(rule, details.x, details.y, true);
> > break;
> > + case 'whereIsIt':
>
> This grew on me (another option might be 'whereAreYou').
>
Glad!
> @@ +55,5 @@
> > moved = vc.moveToPoint(rule, details.x, details.y, true);
> > break;
> > + case 'whereIsIt':
> > + if (!forwardMessage(vc, aMessage)) {
> > + if (!vc.position && aMessage.json.move)
>
> Why do you check move?
If move is true, move to first object in document when no vc position is set.
![]() |
||
Comment 4•13 years ago
|
||
> > @@ +55,5 @@
> > > moved = vc.moveToPoint(rule, details.x, details.y, true);
> > > break;
> > > + case 'whereIsIt':
> > > + if (!forwardMessage(vc, aMessage)) {
> > > + if (!vc.position && aMessage.json.move)
> >
> > Why do you check move?
>
> If move is true, move to first object in document when no vc position is set.
OK I assume a whereIsIt with move not true might happen sometime?
![]() |
||
Updated•13 years ago
|
Attachment #672086 -
Flags: review?(dbolter) → review+
Assignee | ||
Comment 5•13 years ago
|
||
Assignee: nobody → eitan
Comment 6•13 years ago
|
||
Status: NEW → RESOLVED
Closed: 13 years ago
Flags: in-testsuite-
Resolution: --- → FIXED
Target Milestone: --- → mozilla19
Comment 7•13 years ago
|
||
Verified fixed in the 2012-10-20 nightly build. Together with bug 802280, this causes nice feedback when switching tabs.
Status: RESOLVED → VERIFIED
Comment 8•13 years ago
|
||
Comment on attachment 672086 [details] [diff] [review]
Report virtual cursor position on selected tab when tab changes, or when focus moves to content area.
[Approval Request Comment]
Bug caused by (feature/regressing bug #): OOP a11y reorg for B2G.
User impact if declined: Users won't hear any feedback, and get inaccurate representations, when switching tabs.
Testing completed (on m-c, etc.): Yes.
Risk to taking this patch (and alternatives if risky): None known.
String or UUID changes made by this patch: None. This bug must be taken along with bug 802280.
Attachment #672086 -
Flags: approval-mozilla-aurora?
Updated•13 years ago
|
Attachment #672086 -
Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Assignee | ||
Comment 9•13 years ago
|
||
Updated•13 years ago
|
status-firefox18:
--- → fixed
status-firefox19:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•