Closed Bug 344392 Opened 15 years ago Closed 15 years ago

Prefer markup over frame type for determining HTML accessibles

Categories

(Core :: Disability Access APIs, defect)

x86
All
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: aaronlev, Assigned: aaronlev)

References

Details

(Keywords: access)

Attachments

(1 file)

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: 15 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.