Add condition for checking AXExpanded on mac.

Add condition for checking AXExpanded on mac.
The problem is that AXExpanded appears for all elements on mac.
This patch adds condition to add AXExpanded with expanded state and
collapsed state.

BUG=98982
Committed: https://crrev.com/f3b521494222905622ef84d56c93e327ef35d8c9
Cr-Commit-Position: refs/heads/master@{#303799}

[je_julie(Not used), 2014-11-11 10:48:41]

je_julie.kim@samsung.com changed reviewers:
+ dmazzoni@chromium.org

[je_julie(Not used), 2014-11-11 10:50:59]

Hi Dominic,

This patch adds condition for checking AXExpanded on mac.
Previously it was added for all elements on mac.
PTAL.

[dmazzoni, 2014-11-12 06:20:13]

The CQ bit was checked by dmazzoni@chromium.org

[dmazzoni, 2014-11-12 06:20:14]

lgtm

[commit-bot: I haz the power, 2014-11-12 06:21:19]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/712293003/20001

[commit-bot: I haz the power, 2014-11-12 07:37:59]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2014-11-12 07:38:36]

Patchset 2 (id:??) landed as
https://crrev.com/f3b521494222905622ef84d56c93e327ef35d8c9
Cr-Commit-Position: refs/heads/master@{#303799}

[faulkner.steve, 2015-02-13 16:22:01]

On Wednesday, 12 November 2014 07:38:38 UTC, commi...@chromium.org wrote:
>
> Patchset 2 (id:??) landed as 
> https://crrev.com/f3b521494222905622ef84d56c93e327ef35d8c9 
> Cr-Commit-Position 
>
<https://crrev.com/f3b521494222905622ef84d56c93e327ef35d8c9Cr-Commit-Position>:

> refs/heads/master@{#303799} 
>
> https://codereview.chromium.org/712293003/ 
>

Hi, this patch (I think) causes VoiceOver to announce the expanded=0 
("collapsed") state for all elements. I tested latest stable chrome on Mac 
and verified the behaviour.  Here is an demo of the behaviour on the 
bbc.co.uk web site http://quick.as/zqatp1x as reported 
by https://twitter.com/katrinkerber

To unsubscribe from this group and stop receiving emails from it, send an email
to chromium-reviews+unsubscribe@chromium.org.

[dmazzoni, 2015-02-13 17:35:57]

Thanks, Steve! I'm not seeing this behavior in Chrome 41 and higher so it sounds
possible the bug was fixed but the bad patch ended up in Chrome 40. Looking into
it now...

[dmazzoni, 2015-02-13 17:39:22]

Ah, yes - looks like
(1) this broke with this patch on Oct 30:
https://codereview.chromium.org/665843002
(2) then we branched for Chrome 40 on Nov 7
(3) then this change fixed it, on Nov 11th.

Annoying that this slipped through! I'll look into a patch to Chrome 40, but
either way Chrome 41 comes out in ~2 weeks.

[faulkner.steve, 2015-02-13 18:03:31]

On 2015/02/13 17:39:22, dmazzoni wrote:
> Ah, yes - looks like
> (1) this broke with this patch on Oct 30:
> https://codereview.chromium.org/665843002
> (2) then we branched for Chrome 40 on Nov 7
> (3) then this change fixed it, on Nov 11th.
> 
> Annoying that this slipped through! I'll look into a patch to Chrome 40, but
> either way Chrome 41 comes out in ~2 weeks.

Cool thanks for chasing it up!

[je_julie(Not used), 2015-02-15 14:41:02]

On 2015/02/13 18:03:31, faulkner.steve wrote:
> On 2015/02/13 17:39:22, dmazzoni wrote:
> > Ah, yes - looks like
> > (1) this broke with this patch on Oct 30:
> > https://codereview.chromium.org/665843002
> > (2) then we branched for Chrome 40 on Nov 7
> > (3) then this change fixed it, on Nov 11th.
> > 
> > Annoying that this slipped through! I'll look into a patch to Chrome 40, but
> > either way Chrome 41 comes out in ~2 weeks.
> 
> Cool thanks for chasing it up!

Thanks, Dominic and Steve and sorry for the problem.
If it needs any further investigation, please let me know.