Reported by mdcurran on 2015-01-22 06:32
In the MSHTML VBufBackend: If a node is marked with visibility:hidden, its child text nodes are correctly not rendered. However, if after rendering its other node descendants yields no content in the virtualBuffer for that node, then we fal back to the node's accessible name or equivilant. We should not do this for nodes with visibility:hidden. This is causing NVDA to render large chunks of content such as collapsed navigation lists, or error messages, when they have been marked as visibility:hidden.
Reported by mdcurran on 2015-01-22 06:32
In the MSHTML VBufBackend: If a node is marked with visibility:hidden, its child text nodes are correctly not rendered. However, if after rendering its other node descendants yields no content in the virtualBuffer for that node, then we fal back to the node's accessible name or equivilant. We should not do this for nodes with visibility:hidden. This is causing NVDA to render large chunks of content such as collapsed navigation lists, or error messages, when they have been marked as visibility:hidden.