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

Joanmarie Diggs <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected],
                   |                            |[email protected]

--- Comment #6 from Joanmarie Diggs <[email protected]> ---
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
[email protected]
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

Reply via email to