MSHTML: inappropriate content is rendered for nodes with visibility:hidden #4839

Closed
nvaccessAuto opened this Issue Jan 22, 2015 · 3 comments

Comments

Projects
None yet
1 participant
@nvaccessAuto

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.

@nvaccessAuto

This comment has been minimized.

Show comment Hide comment
@nvaccessAuto

nvaccessAuto Jan 22, 2015

Comment 1 by Michael Curran <mick@... on 2015-01-22 06:36
In [c9f40bd]:

Merge branch 't4839' into next. Incubates #4839

Changes:
Added labels: incubating

Comment 1 by Michael Curran <mick@... on 2015-01-22 06:36
In [c9f40bd]:

Merge branch 't4839' into next. Incubates #4839

Changes:
Added labels: incubating

@nvaccessAuto

This comment has been minimized.

Show comment Hide comment
@nvaccessAuto

nvaccessAuto Jan 22, 2015

Comment 2 by jteh on 2015-01-22 21:24
This is one instance of #3776. Can this same idea be applied to fix other instances of hidden content?

Comment 2 by jteh on 2015-01-22 21:24
This is one instance of #3776. Can this same idea be applied to fix other instances of hidden content?

@nvaccessAuto

This comment has been minimized.

Show comment Hide comment
@nvaccessAuto

nvaccessAuto Feb 5, 2015

Comment 3 by Michael Curran <mick@... on 2015-02-05 00:23
In [5c2b8d1]:

Merge branch 't4839'. Fixes #4839

Changes:
Removed labels: incubating
State: closed

Comment 3 by Michael Curran <mick@... on 2015-02-05 00:23
In [5c2b8d1]:

Merge branch 't4839'. Fixes #4839

Changes:
Removed labels: incubating
State: closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment