Adobe Reader: Prefer name over text content for buttons

[nvaccessAuto]

Reported by jteh on 2013-11-12 06:15
Issue raised by Adobe.

For some buttons, IPDDomNode::GetTextContent returns something different to the name. GetTextContent is supposed to account for alternate and actual text, but it seems that overriding a button's name is not considered alternate/actual text. Apparently, authors can override the name using the tooltip and this is what they (and Adobe) expect an AT user to see.

I guess it makes sense to do this for all controls for which the name is generally the content; i.e. the useNameAsContent flag in the backend.

[nvaccessAuto]

Comment 2 by James Teh <jamie@... on 2013-11-13 03:12
In [d196b3f]:

In browse mode in Adobe Reader, the correct text is now rendered for buttons, etc. where the label has been overridden using a tooltip or other means.

In the backend, where useNameAsContent is true, IPDDomNode::GetName is now tried before IPDDomNode::GetTextContent.
Re #3640.

[nvaccessAuto]

Comment 3 by James Teh <jamie@... on 2013-11-13 03:13
In [d6ad6ba]:

Merge branch 't3640' into next

Incubates #3640.

Changes:
Added labels: incubating

[nvaccessAuto]

Comment 6 by James Teh <jamie@... on 2013-11-26 22:59
In [0b55f19]:

In browse mode in Adobe Reader, the correct text is now rendered for buttons, etc. where the label has been overridden using a tooltip or other means.

In the backend, where useNameAsContent is true, IPDDomNode::GetName is now tried before IPDDomNode::GetTextContent.
Fixes #3640.

Changes:
Removed labels: incubating
State: closed

[nvaccessAuto]

Comment 7 by jteh on 2013-11-26 23:04
Changes:
Milestone changed from next to 2014.1