Summary: | MSAA: WebKit reports the document state as disabled | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Jon Honeycutt <jhoneycutt> | ||||||
Component: | Accessibility | Assignee: | Jon Honeycutt <jhoneycutt> | ||||||
Status: | RESOLVED FIXED | ||||||||
Severity: | Normal | CC: | jeffm | ||||||
Priority: | P2 | Keywords: | InRadar, PlatformOnly | ||||||
Version: | 528+ (Nightly build) | ||||||||
Hardware: | PC | ||||||||
OS: | Windows 7 | ||||||||
Attachments: |
|
Description
Jon Honeycutt
2011-09-12 17:38:19 PDT
Created attachment 107123 [details]
Patch
Comment on attachment 107123 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=107123&action=review > Source/WebCore/ChangeLog:5 > + <rdar://problem/10095898> A one sentence description of what was causing the bug would be useful here, i.e. why using isEnabled() for AccessibilityScrollView doesn't work in this case. Comment on attachment 107123 [details]
Patch
Looks OK to me. I agree with Jeff that this is missing an explanation of why it is necessary to treat documents as enabled in some cases but specifically not for MSAA.
Actually, I can't think of a reason for MSAA to have a special path. I'm going to post a patch that just makes AccessibilityScrollView override isEnabled() and return true. Created attachment 107245 [details]
Patch v2
Simpler fix.
Landed in <http://trac.webkit.org/changeset/95056>. |