Track tasks and feature requests
Join 36 million developers who use GitHub issues to help identify, assign, and keep track of the features and bug fixes your projects need.
Sign up for free See pricing for teams and enterprisesAdobe Reader: Inherited language lost when node is updated #2544
Comments
This comment has been minimized.
This comment has been minimized.
|
Comment 2 by jteh on 2012-07-26 03:39 |
nvaccessAuto
added
bug
Browse mode
PDFUAWork
AdobeWork
labels
Nov 10, 2015
nvaccessAuto
assigned
jcsteh
Nov 10, 2015
nvaccessAuto
added this to the 2012.3 milestone
Nov 10, 2015
nvaccessAuto
closed this
Nov 10, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
nvaccessAuto commentedJul 20, 2012
Reported by jteh on 2012-07-20 05:05
In Adobe Reader, if a node doesn't explicitly specify its language, it is inherited from the nearest ancestor that does. However, if such a node is re-rendered due to an event, the inherited language will be lost. This is because the node is rendered into a temporary buffer, so it isn't linked to its ancestors yet.
Unfortunately, the problem is more visible than just forms, etc. because Reader fires a valueChange event on the top node of a page when it scrolls. Thus, whenever you switch to a new page, the inherited language is lost for the top node of that page.