Closed Bug 344392 Opened 18 years ago Closed 18 years ago

Prefer markup over frame type for determining HTML accessibles

Categories

(Core :: Disability Access APIs, defect)

Product:
Core
Component:
Disability Access APIs
Platform:
x86
All
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: aaronlev, Assigned: aaronlev)

References

Details

(Keywords: access)

Attachments

(1 file)

First check for role=presentation, then check for accessible by markup type, then check for accessible by frame type (if HTML), finally check to see if generic accessible needed
8.70 KB, patch
ginnchen+exoracle
: review+
Details | Diff | Splinter Review 
Currently the frame type always gets the first chance to say if and what kind of accessible should be created, via nsIFrame::GetAccessible()

After that we call CreateHTMLAccessibleByMarkup() to catch specialized cases based on the markup.

We're doing this in the wrong order. The problem shows up under newatk where things like nsHyperTextAccessible get created for an <option>, because they use nsBlockFrame.
Attachment #228982 - Flags: review?(ginn.chen) → review+
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: