Active Accessibility: support ROLE_DIALOG for <dialog>'s

RESOLVED FIXED

Status

SeaMonkey
General
RESOLVED FIXED
16 years ago
13 years ago

People

(Reporter: Aaron Leventhal, Assigned: Aaron Leventhal)

Tracking

({access, sec508})

Trunk
x86
Windows 2000
access, sec508

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

16 years ago
Normally we use ROLE_PANE for a document level object. However, for MSAA we
should support ROLE_DIALOG. Now that we know what's a dialog via <dialog> tags,
we should support ROLE_DIALOG
(Assignee)

Updated

16 years ago
Keywords: access, nsbeta1, sec508
(Assignee)

Comment 1

16 years ago
Created attachment 73106 [details] [diff] [review]
Supports ROLE_DIALOG if root element is a <dialog>

Updated

16 years ago
Keywords: nsbeta1 → nsbeta1+

Comment 2

16 years ago
Comment on attachment 73106 [details] [diff] [review]
Supports ROLE_DIALOG if root element is a <dialog>

r=jgaunt
Attachment #73106 - Flags: review+

Comment 3

16 years ago
Comment on attachment 73106 [details] [diff] [review]
Supports ROLE_DIALOG if root element is a <dialog>

sr=alecf
Attachment #73106 - Flags: superreview+

Comment 4

16 years ago
Comment on attachment 73106 [details] [diff] [review]
Supports ROLE_DIALOG if root element is a <dialog>

a=asa (on behalf of drivers) for checkin to the 1.0 trunk
Attachment #73106 - Flags: approval+
(Assignee)

Comment 5

16 years ago
fix checked in
Status: NEW → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → FIXED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.