Closed Bug 684818 Opened 13 years ago Closed 13 years ago

shift+tab fails on editable document after context menu is closed: enable mochitest

Categories

(Core :: DOM: UI Events & Focus Handling, defect)

x86
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla10

People

(Reporter: surkov, Assigned: surkov)

References

Details

(Keywords: access)

Attachments

(2 files)

Attached file testcase
spun off bug 550338:

1. Focus the editable document.
2. Open context menu (press the applications key, shift+F10 or right click)
3. Dismiss context menu (press escape or alt key)
4. Press shift+tab
  Actual: Nothing happens.
Neil's bug 550338 comment #8:
The second set of steps (5-9) look like an unrelated bug, which has to do with confusion over what should be focused in editable documents. Bug 544277 is an example of a bug related to this.
No longer blocks: 550338
Seems to be fixed in the last try build for bug 673958.
Depends on: 673958
fixed by bug 673958
Assignee: nobody → surkov.alexander
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla10
(In reply to alexander surkov from comment #3)
> fixed by bug 673958

It's really fixed but I bet that wasn't bug 673958.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Summary: shift+tab fails on editable document after context menu is closed → shift+tab fails on editable document after context menu is closed: enable mochitest
Attached patch patchSplinter Review
Attachment #563274 - Flags: review?(marco.zehe)
Comment on attachment 563274 [details] [diff] [review]
patch

r=me. So which bug fixed this one?
Attachment #563274 - Flags: review?(marco.zehe) → review+
This sounds awfully similar to bug 550338, which *was* fixed by bug 673958, so I think this is actually a dupe of bug 550338. The later steps of bug 550338 provide this exact testcase.
(In reply to Marco Zehe (:MarcoZ) from comment #7)
> This sounds awfully similar to bug 550338

Marco, this bug is spun off the bug 550338 :), in other words, I filed it to keep  keyboard navigation issue separately from disability access problems. Eventually the problem was fixed (and our focus rework is not guilty of that). 

I'll enable mochitest to make sure it won't regress.
landed on inbound https://hg.mozilla.org/integration/mozilla-inbound/rev/be9874f75bae

I disabled the test on linux since due to some reason shift + tab doesn't work on linux in this case.

Trevor, when you get some time then could you please check it and file new bug?
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
Flags: in-testsuite+
Depends on: 718235
Version: unspecified → Trunk
Component: Keyboard: Navigation → User events and focus handling
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: