[Libreoffice-bugs] [Bug 91739] nvda can not read documents from top to bottom.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=91739

--- Comment #18 from QA Administrators  ---
Dear zahra,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 91739] nvda can not read documents from top to bottom.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=91739

Michael Weghorn  changed:

   What|Removed |Added

   See Also||https://github.com/nvaccess
   ||/nvda/issues/4119
 CC||m.wegh...@posteo.de

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 91739] nvda can not read documents from top to bottom.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=91739

--- Comment #17 from V Stuart Foote  ---
(In reply to QA Administrators from comment #16)

This is still an issue, no change supporting structural navigation by page top
to bottom with current release or on master. NVDA screen reader exhausts buffer
and stalls.

Here are links to some related historical reading from the Gnome ATK/AT-SPI
side on providing support for the Accessibility::Collection IDL
(AtkDocument/AtkCollection) as a possible solution to our limited window into a
complex document that disrupts screen reading.

https://bugzilla.gnome.org/show_bug.cgi?id=652548
https://bugzilla.gnome.org/show_bug.cgi?id=345750

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 91739] nvda can not read documents from top to bottom.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=91739

--- Comment #16 from QA Administrators  ---
Dear zahra,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 91739] nvda can not read documents from top to bottom.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=91739

--- Comment #15 from V Stuart Foote  ---
(In reply to QA Administrators from comment #14)
This is still an issue, no change supporting structural navigation by page top
to bottom with current release or on master. NVDA screen reader exhausts buffer
and stalls.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 91739] nvda can not read documents from top to bottom.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=91739

--- Comment #14 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 91739] nvda can not read documents from top to bottom.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=91739

V Stuart Foote  changed:

   What|Removed |Added

 CC||michael.me...@collabora.com
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=35
   ||652,
   ||https://bz.apache.org/ooo/s
   ||how_bug.cgi?id=117542

--- Comment #13 from V Stuart Foote  ---
Here are links to some related historical reading from the Gnome ATK/AT-SPI
side on providing support for the Accessibility::Collection IDL
(AtkDocument/AtkCollection) as a possible solution to our limited window into a
complex document that disrupts screen reading.

https://bugzilla.gnome.org/show_bug.cgi?id=652548
https://bugzilla.gnome.org/show_bug.cgi?id=345750

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 91739] nvda can not read documents from top to bottom.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=91739

--- Comment #12 from V Stuart Foote  ---
This is still an issue, no change supporting structural navigation by page top
to bottom with current release or on master. NVDA screen reader exhausts buffer
and stalls.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 91739] nvda can not read documents from top to bottom.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=91739

--- Comment #11 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present on a currently supported version of
LibreOffice 
(5.1.6 or 5.2.3  https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of
LibreOffice and 
your operating system, and any changes you see in the bug behavior

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave 
a short comment that includes your version of LibreOffice and Operating System

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3)

http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to "inherited from OOo";
4b. If the bug was not present in 3.3 - add "regression" to keyword


Feel free to come ask questions or to say hello in our QA chat:
http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug-20170103

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 91739] nvda can not read documents from top to bottom.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=91739

Robinson Tryon (qubit)  changed:

   What|Removed |Added

   Keywords||accessibility
 Whiteboard|a11y|

--- Comment #10 from Robinson Tryon (qubit)  ---
Migrating Whiteboard tags to Keywords: (a11y -> accessibility)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 91739] nvda can not read documents from top to bottom.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=91739

--- Comment #9 from Jacobo Aragunde Pérez  ---
(In reply to Joanmarie Diggs from comment #6)
> 
> For each page in the document, create an accessible (ATK_ROLE_PAGE on my
> platform; dunno about IA2). Regardless of the role, these page accessibles
> are all immediate children of the document and are all created upon document
> load. Also load the accessible children for a given page when that page is
> accessed. Lazy load the rest of the children of each page.

Unfortunately, this approach seems to be difficult to implement. There is no
concept of "pages" in the document model; pages are an artifact of the view
that wraps the contents. There are contents that can be split between two
pages, so we would still have to do some hacks to model the contents in a
proper tree. Finally, the flow of paragraphs to/from the next/previous page
when editions happen would have to trigger a rebuild of parts of the
accessibility tree, this should be doable but it's definitely inconvenient and
would probably generate a lot of event noise.


> Page 1 (which is visible)
> * Paragraph 1
> * Paragraph 2
> Page 2 (not currently visible)
> * Paragraph 3
> * Paragraph 4
> 
> At least on my platform, if you get the last child of the accessible
> document, you get "Paragraph 2". If you then get the flows-to target of that
> child you get "Paragraph 3". So far so good. But if you get the parent of
> "Paragraph 3" you get the accessible document which contains "Paragraph 1"
> and "Paragraph 2". In other words, the parent of "Paragraph 3" does not have
> "Paragraph 3" as a child. That's a broken tree.

When the paragraph 3 is got through the flows-to relation, is the parent
component (the document) refreshed? Would that work to implement "say all"?

> This issue also impacts things like Orca's ability to do structural
> navigation (navigate amongst headings, for instance).

Regarding this topic, would it help if we implemented flows to/from relations
among header objects?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 91739] nvda can not read documents from top to bottom.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=91739

--- Comment #8 from Jacobo Aragunde Pérez  ---
The accessible role PAGE seems to exist in LibreOffice internal FW [1], but
I've done some grepping and I think it's never used.

[1]
http://api.libreoffice.org/docs/idl/ref/namespacecom_1_1sun_1_1star_1_1accessibility_1_1AccessibleRole.html#a29bb572b50678c1b43fb73f8e0855d65

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 91739] nvda can not read documents from top to bottom.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=91739

V Stuart Foote vstuart.fo...@utsa.edu changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=93
   ||463

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 91739] nvda can not read documents from top to bottom.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=91739

V Stuart Foote vstuart.fo...@utsa.edu changed:

   What|Removed |Added

 CC||borisdu...@cmail.cz,
   ||b...@eikota.de

--- Comment #7 from V Stuart Foote vstuart.fo...@utsa.edu ---
(In reply to Joanmarie Diggs from comment #6)

 I understand the desire to not automatically expose the entire tree for all
 pages at once because that potentially would be a huge and non-performant
 solution. But in addition to a non-broken tree, I'd really like to have
 structural navigation for document content in Orca. And not everything has
 an immediate flows-to (tables, form fields). So what about something like:
 
 For each page in the document, create an accessible (ATK_ROLE_PAGE on my
 platform; dunno about IA2). Regardless of the role, these page accessibles
 are all immediate children of the document and are all created upon document
 load. Also load the accessible children for a given page when that page is
 accessed. Lazy load the rest of the children of each page.

IAccessible2 has the same... IA2_ROLE_PAGE, but it looks like NSAccessibility
does not currently map it in any useful fashion, refs.

=-refs-=
IA2_ROLE_PAGE
http://opengrok.libreoffice.org/xref/core/winaccessibility/source/UAccCOMIDL/ia2_api_all.idl#901
http://opengrok.libreoffice.org/xref/core/winaccessibility/source/service/AccObject.cxx

NSAccessibility
http://opengrok.libreoffice.org/xref/core/vcl/osx/a11yrolehelper.mm#119
https://developer.apple.com/library/mac/documentation/AppKit/Reference/NSAccessibility_Protocol_Reference/index.html#//apple_ref/doc/constant_group/Roles

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 91739] nvda can not read documents from top to bottom.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=91739

Joanmarie Diggs jdi...@igalia.com changed:

   What|Removed |Added

 CC||jaragu...@igalia.com,
   ||jdi...@igalia.com

--- Comment #6 from Joanmarie Diggs jdi...@igalia.com ---
This issue also impacts things like Orca's ability to do structural navigation
(navigate amongst headings, for instance).

As for the flows-to relations, things get more interesting depending on what
you are trying to accomplish. Consider something like:

Page 1 (which is visible)
* Paragraph 1
* Paragraph 2
Page 2 (not currently visible)
* Paragraph 3
* Paragraph 4

At least on my platform, if you get the last child of the accessible document,
you get Paragraph 2. If you then get the flows-to target of that child you
get Paragraph 3. So far so good. But if you get the parent of Paragraph 3
you get the accessible document which contains Paragraph 1 and Paragraph 2.
In other words, the parent of Paragraph 3 does not have Paragraph 3 as a
child. That's a broken tree.

I understand the desire to not automatically expose the entire tree for all
pages at once because that potentially would be a huge and non-performant
solution. But in addition to a non-broken tree, I'd really like to have
structural navigation for document content in Orca. And not everything has an
immediate flows-to (tables, form fields). So what about something like:

For each page in the document, create an accessible (ATK_ROLE_PAGE on my
platform; dunno about IA2). Regardless of the role, these page accessibles are
all immediate children of the document and are all created upon document load.
Also load the accessible children for a given page when that page is accessed.
Lazy load the rest of the children of each page.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 91739] nvda can not read documents from top to bottom.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=91739

--- Comment #5 from James Teh ja...@nvaccess.org ---
LO *does* expose flowsFrom and flowsTo via IA2. The issue isn't that they
aren't exposed. The issue is that they don't expose paragraphs that are
currently off-screen in some cases.

So, steps to reproduce with the attached example document:
1. Open the document. The cursor will be at the first line.
2. Get the accessible for the first paragraph.
3. Call IAccessible::nRelations.
Result (correct): 1
4. Call IAccessible2::relations, passing 1 for maxRelations.
5. Get the first (and only) IAccessibleRelation returned.
6. On the relation from step 5, call IAccessibleRelation::relationType.
Result (correct): flowsTo
7. On the relation from step 5, call IAccessibleRelation::nTargets.
Result (correct): 1
8. On the relation from step 5, call IAccessibleRelation::target, passing 0 for
targetIndex.
Expected: An IUnknown for the second paragraph.
Actual: E_FAIL
9. In the document, press control+downArrow to move to the second paragraph.
10. On the relation from step 5, call IAccessibleRelation::target, passing 0
for targetIndex.
Result (correct): An IUnknown for the second paragraph.

Interestingly, if you then press control+home to move to the top of the
document and repeat step 10, you still get the second paragraph. So, it seems
that if you've retrieved the paragraph once already, you can retrieve it again
even if it goes off-screen.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 91739] nvda can not read documents from top to bottom.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=91739

--- Comment #3 from James Teh ja...@nvaccess.org ---
Say all for Symphony (NVDA ticket #910) was fixed years ago. Any remaining
issues were due to bugs in Symphony.

The problem with say all in OO/LO is due to the fact that they only expose text
that is currently on screen. As a result, once NVDA say all gets to the last
paragraph, it asks for the next paragraph and is told that there isn't one, so
say all can't go any further. There are hacks to get around this (e.g. send
control+downArrow or scroll in some other way when LO reports no more
paragraphs), but this is fairly inelegant and potentially unreliable. Whether
this is a bug is debatable, but it's certainly a problem for us and is not what
happens in other implementations. In Symphony, you could get at paragraphs that
weren't yet on screen (barring weird bugs), which is why say all worked in
Symphony.

Note that you don't have to generate accessibles for every paragraph in the
document ahead of time. You could just generate them on demand when the flowsTo
relation is required.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 91739] nvda can not read documents from top to bottom.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=91739

V Stuart Foote vstuart.fo...@utsa.edu changed:

   What|Removed |Added

   See Also||https://bz.apache.org/ooo/s
   ||how_bug.cgi?id=27138

--- Comment #4 from V Stuart Foote vstuart.fo...@utsa.edu ---
@Jamie, *,

This gets beyond my skill set pretty quickly...

But, looking at i27138 - we already have an XAccessibleContext providing
flowsFrom and flowsTo in the internal UAA. And that should be providing the
IAccessible2 relationships.

But, seems that  for our Windows implementation--UAccCOM--we may be defining
just the parent and child relationships, and not actually defining
IA2_RELATION_FLOWS_FROM and IA2_RELATION_FLOWS_TO (see refs).

Anyone have a better feel for the this?

@Jamie,  if the IA2_RELATION_FLOWS_FROM and IA2_RELATION_FLOWS_TO are fully
instrumented, would that then facilitate the NVDA SayAll function?

=-refs-=
Core
http://opengrok.libreoffice.org/xref/core/accessibility/source/extended/textwindowaccessibility.cxx#1447
http://opengrok.libreoffice.org/xref/core/sw/source/core/access/accpara.hxx#265
http://opengrok.libreoffice.org/xref/core/sw/source/core/access/accpara.cxx#959
http://opengrok.libreoffice.org/xref/core/editeng/source/accessibility/AccessibleEditableTextPara.cxx#813

Windows IA2 UAccCOM
http://opengrok.libreoffice.org/xref/core/winaccessibility/source/UAccCOMIDL/UAccCOM.idl
http://opengrok.libreoffice.org/xref/core/winaccessibility/source/UAccCOM/MAccessible.cxx
http://opengrok.libreoffice.org/xref/core/winaccessibility/source/UAccCOMIDL/ia2_api_all.idl#354

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 91739] nvda can not read documents from top to bottom.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=91739

--- Comment #1 from zahra nasrinkhaks...@gmail.com ---
Created attachment 116166
  -- https://bugs.documentfoundation.org/attachment.cgi?id=116166action=edit
one text to confirm the problem.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 91739] nvda can not read documents from top to bottom.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=91739

V Stuart Foote vstuart.fo...@utsa.edu changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 CC||ja...@nvaccess.org,
   ||vstuart.fo...@utsa.edu
 Ever confirmed|0   |1
 Whiteboard||a11y

--- Comment #2 from V Stuart Foote vstuart.fo...@utsa.edu ---
Setting new, but believe this remains an issue with NVDAs support for parsing
IAccessible2 based content.

This has an open issue on NVDA support:
http://community.nvda-project.org/ticket/4119 or with Symphony's early IA2
based support NVDA in ticket 910. But issues with SayAll with ODF and
OpenOffice existed back to the JavaAccessBridge/JRE Java Accessibility era--see
NVDA tickets 422, 96

@Jamie, any thoughts on implementing SayAll for LibreOffice/Apache OpenOffice
or, should I just close this not our bug?

Stuart

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 91739] nvda can not read documents from top to bottom.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=91739

V Stuart Foote vstuart.fo...@utsa.edu changed:

   What|Removed |Added

  Component|ux-advise   |UI
 Blocks||60251

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 91739] nvda can not read documents from top to bottom.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=91739

V Stuart Foote vstuart.fo...@utsa.edu changed:

   What|Removed |Added

 OS|All |Windows (All)
   Severity|major   |normal

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs