Check RendererAccessibility mode instead of WebKit accessibilityEnabled.

Check RendererAccessibility mode instead of WebKit accessibilityEnabled.

We were hitting an assertion failure that indicated that WebKit accessibility
was enabled, but RendererAccessibility's mode was that accessibility is off.
Note that WebKit accessibility is a global flag, once enabled, it is never
turned off. This could happen if a new RenderViewImpl is created in the
same process where WebKit accessibility was previously enabled, but the
newly-created RendererAccessibility mode is off.

The fix is to never call handle accessibility notifications if
RendererAccessibility's mode is off, regardless of WebKit's accessibility
notification flag.

BUG=123649
TEST=none


Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=133489

[dmazzoni, 2012-04-23 08:23:29]

dtseng: primary review
avi: OWNERS review for content/

[Avi (use Gerrit), 2012-04-23 14:48:27]

owner LGTM

[David Tseng, 2012-04-23 16:32:00]

lgtm

[commit-bot: I haz the power, 2012-04-23 16:48:43]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/dmazzoni@chromium.org/10162028/1

[commit-bot: I haz the power, 2012-04-23 18:59:33]

Change committed as 133489