No caret events in CSS scrollable area

RESOLVED FIXED

Status

()

Core
Disability Access APIs
RESOLVED FIXED
11 years ago
11 years ago

People

(Reporter: Aaron Leventhal, Assigned: Aaron Leventhal)

Tracking

(Blocks: 1 bug, {access, sec508})

Trunk
access, sec508
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Assignee)

Description

11 years ago
Created attachment 266928 [details]
CSS overflow testcase

Caret events are not being correctly fired in DOM nodes made accessible because they are scrollable (and thus need to be focusable so keyboard users can scroll them).

Load the attached testcase and turn on caret browsing. Caret move events will not be fired for the object.
(Assignee)

Comment 1

11 years ago
Created attachment 266929 [details] [diff] [review]
Use nsHyperTextAccessibleWrap (which inherits from nsAccessibleWrap) for generic HTML container accessibles instead of nsAccessibleWrap. It supports the caret and selection.
Attachment #266929 - Flags: review?(surkov.alexander)

Comment 2

11 years ago
Comment on attachment 266929 [details] [diff] [review]
Use nsHyperTextAccessibleWrap (which inherits from nsAccessibleWrap) for generic HTML container accessibles instead of nsAccessibleWrap. It supports the caret and selection.

I guess it's ok to create hypertext accessible for all frames we have not enough info about. Though probably we should get rid CreateHTMLGenericAccessible at all, or is it better to keep it for possible future changes?
Attachment #266929 - Flags: review?(surkov.alexander) → review+
(Assignee)

Comment 3

11 years ago
I filed bug 382966 for that cleanup -- we only need one of those methods.
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.