(Spun off from bug 91739 comment #6)
Steps to reproduce:
1. Create a document with the following structure:
Page 1 (which is visible)
* Paragraph 1
* Paragraph 2
Page 2 (not currently visible)
* Paragraph 3
* Paragraph 4
2. Use Accerciser or an pyatspi script to get the last child of the document. (Result: "Paragraph 2")
3. Get the flows-to target of that child (Result: "Paragraph 3")
So far so good.
4. Get the parent of "Paragraph 3" (Result: 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.
Ideally, the children of the document would be accessible pages. And the children of those accessible pages would be the document's paragraphs (and headings and lists and ...). Failing that, it would be extremely helpful if:
1. As paragraphs are accessed via the flows-to/flows-from accessible relation, they are added to the document's children.
2. As paragraphs are scrolled off-screen, they are NOT removed from the list of the document's children.
Hopefully by doing the above along with emitting the appropriate accessible events (see bug 96490), the accessible tree will be more reliable.
(In reply to Joanmarie Diggs from comment #0)
> 2. Use Accerciser or an pyatspi script to get the last child of the
> document. (Result: "Paragraph 2")
> 3. Get the flows-to target of that child (Result: "Paragraph 3")
> So far so good.
> 4. Get the parent of "Paragraph 3" (Result: The accessible document which
> contains "Paragraph 1" and "Paragraph 2")
How do we do this in Accerciser?
Set to NEEDINFO.
Change back to UNCONFIRMED after you have provided the information.
(In reply to Buovjaga from comment #1)
> (In reply to Joanmarie Diggs from comment #0)
> > 2. Use Accerciser or an pyatspi script to get the last child of the
> > document. (Result: "Paragraph 2")
Quit Accerciser if it is running, create the document first with only page 1 showing, then launch Accerciser. In the pane on the left you should find two children of the document accessible. You can verify which paragraphs they are by expanding Text (Editable) in the Interface Viewer.
> > 3. Get the flows-to target of that child (Result: "Paragraph 3")
You can examine relations in the interface viewer (expand Accessible). But to do the subsequent tasks, iPython console is probably better. So....
Select paragraph 2 in the pane on the left and switch to the iPython console. Type the following:
r = acc.getRelationSet()
flowsToRelations = [x for x in r if x.getRelationType() == RELATION_FLOWS_TO]
target = flowsToRelations.getTarget(0)
The result I get is 'Paragraph 3'. So target is the third paragraph. With this in mind....
> > 4. Get the parent of "Paragraph 3" (Result: The accessible document which
> > contains "Paragraph 1" and "Paragraph 2")
Still in the iPython console:
parent = target.parent
children = [x.queryText().getText(0,-1) for x in parent]
The result I get is ['Paragraph 1', 'Paragraph 2'].
So the parent of 'Paragraph 3' has two children, neither of which is 'Paragraph 3'.
Ok, now I could reproduce.
Note for testers: when you have launched Accerciser after creating the document, in the node view you should have:
-[no title] (panel)
--Untitled (root pane)
and then a whole bunch of nodes.
Now look at the panel with 3 children. It has a child that is "scroll pane".
This scroll pane has a child of the type "document text".
This document text has children of the type "paragraph".
64-bit, KDE Plasma 5
Build ID: 18.104.22.168 Arch Linux build-1
CPU Threads: 8; OS Version: Linux 4.5; UI Render: default;
Locale: fi-FI (fi_FI.UTF-8)
** 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.2.7 or 5.3.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)
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!
I can still reproduce this bug on LibreOfficeDev 5.5 from 2017-05-28.