New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Treat objects with the whitespace role as layout #3839

Closed
nvaccessAuto opened this Issue Feb 3, 2014 · 4 comments

Comments

Projects
None yet
1 participant
@nvaccessAuto

nvaccessAuto commented Feb 3, 2014

Reported by jteh on 2014-02-03 02:24
LibreOffice bug 74284 reports that NVDA speaks a lot of whitespace objects in the focus ancestry on the LibreOffice startup screen. The whitespace role should get a presentationType of layout, as it shouldn't appear in either focus ancestry or simple review.

@nvaccessAuto

This comment has been minimized.

nvaccessAuto commented Feb 13, 2014

Comment 1 by James Teh <jamie@... on 2014-02-13 17:38
In [7606dfd]:

Whitespace objects are no longer included in simple review or reported when the focus moves, as they are purely for layout purposes.

Re #3839.

@nvaccessAuto

This comment has been minimized.

nvaccessAuto commented Feb 13, 2014

Comment 2 by James Teh <jamie@... on 2014-02-13 17:39
In [b37b66f]:

Merge branch 't3839' into next

Incubates #3839.

Changes:
Added labels: incubating

@nvaccessAuto

This comment has been minimized.

nvaccessAuto commented Mar 7, 2014

Comment 3 by James Teh <jamie@... on 2014-03-07 06:20
In [1af4364]:

Whitespace objects are no longer included in simple review or reported when the focus moves, as they are purely for layout purposes.

Fixes #3839.

Changes:
Removed labels: incubating
State: closed

@nvaccessAuto

This comment has been minimized.

nvaccessAuto commented Mar 7, 2014

Comment 4 by jteh on 2014-03-07 06:21
Changes:
Milestone changed from next to 2014.2

@nvaccessAuto nvaccessAuto added the bug label Nov 10, 2015

@nvaccessAuto nvaccessAuto added this to the 2014.2 milestone Nov 10, 2015

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