Created attachment 118588 [details] test case Steps to reproduce: 1. Open the attached test case in Writer 2. Launch the attached pyatspi accessible-event listener in a terminal 3. Position the caret in the middle of the last line on the first page 4. Down arrow once then up arrow 5. Position the caret at the start of the last line on the first page 6. Down arrow once then up arrow Expected results: Each time the caret moves into the paragraph on the other page, that paragraph would emit both an object:state-changed:focused event and a caret moved event. Actual results: The expected results *unless* the caret has moved from the start of the paragraph on page 2 to the start of the paragraph on page 1. In that instance, only the caret-moved event is received. Annotated output from performing the steps above: ============== # Step 3: Position caret in middle of last line on first page 18:09:32 - [paragraph | ] with index in parent 11 - is focused. 18:09:32 - [paragraph | ] with index in parent 11 - caret moved to offset 14. # Step 4: Down arrow and up arrow 18:09:35 - [paragraph | ] with index in parent 12 - is focused. 18:09:35 - [paragraph | ] with index in parent 12 - caret moved to offset 14. 18:09:38 - [paragraph | ] with index in parent 11 - is focused. 18:09:38 - [paragraph | ] with index in parent 11 - caret moved to offset 14. # Step 5: Position caret at start of last line on first page 18:09:45 - [paragraph | ] with index in parent 11 - caret moved to offset 0. # Step 6: Down arrow and up arrow 18:09:47 - [paragraph | ] with index in parent 11 - caret moved to offset 70. 18:09:47 - [paragraph | ] with index in parent 12 - is focused. 18:09:47 - [paragraph | ] with index in parent 12 - caret moved to offset 0. 18:09:52 - [paragraph | ] with index in parent 11 - caret moved to offset 0. ==============
Created attachment 118590 [details] accessible-event listener (paragraph.py)
Reproduced. Arch Linux 64-bit, KDE Plasma 5 Version: 5.2.0.0.alpha1+ Build ID: 540fee2dc7553152914f7f1d8a41921e765087ef CPU Threads: 8; OS Version: Linux 4.5; UI Render: default; Locale: fi-FI (fi_FI.UTF-8) Built on April 30th 2016
** 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) 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-20170522
Dear all, I'm not sure to do the right thing but I'm not able to reproduce. Best regards.
Dear all, I can reproduce on LibreOffice 5.4 GTK3 but not on LibreOffice 4.2.6. Add the regression keyword. When I press down arrow from the beginning of the last line of the page to the first line of the second page I observe that LibreOffice emits too much events. 15:31:33 - [paragraph | ] with index in parent 21 - is focused. 15:31:34 - [paragraph | ] with index in parent 21 - caret moved to offset 70. 15:31:34 - [paragraph | ] with index in parent 22 - is focused. 15:31:34 - [paragraph | ] with index in parent 22 - caret moved to offset 0. 15:31:36 - [paragraph | ] with index in parent 22 - is focused. The user consequence: Orca announces the previous and current line when the user switch between page one and page two. Best regards.
** 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
I am not sure if I have reproduced the issue or not; I do not quite understand it. Sorry. Here are my specs and output of the listener: Version: 6.1.2.1 Build ID: 1:6.1.2-0ubuntu1.1 CPU threads: 4; OS: Linux 4.18; UI render: default; VCL: gtk3; Locale: nl-NL (en_US.UTF-8); Calc: group threaded 16:26:43 - [panel | ] with index in parent 1 - is focused. 16:26:43 - [paragraph | ] with index in parent 0 - is focused. 16:26:46 - [paragraph | ] with index in parent 26 - is focused. 16:26:46 - [paragraph | ] with index in parent 26 - caret moved to offset 31. 16:26:46 - [paragraph | ] with index in parent 26 - is focused. 16:26:46 - [paragraph | ] with index in parent 26 - caret moved to offset 31. 16:26:47 - [paragraph | ] with index in parent 27 - is focused. 16:26:47 - [paragraph | ] with index in parent 27 - caret moved to offset 31. 16:26:48 - [paragraph | ] with index in parent 26 - is focused. 16:26:48 - [paragraph | ] with index in parent 26 - caret moved to offset 31. 16:27:42 - [paragraph | ] with index in parent 26 - is focused. 16:27:46 - [paragraph | ] with index in parent 26 - caret moved to offset 0. 16:27:47 - [paragraph | ] with index in parent 26 - caret moved to offset 70. 16:27:47 - [paragraph | ] with index in parent 27 - is focused. 16:27:47 - [paragraph | ] with index in parent 27 - caret moved to offset 0.
@Xisco: This bug description is outdated, there is always a mistake when a paragraph on two pages but it's not the same bug, see comment #5. Do we need to open a new update or is it possible to update the description ? Best regards, Alex.
(In reply to Alex ARNAUD from comment #8) > @Xisco: This bug description is outdated, there is always a mistake when a > paragraph on two pages but it's not the same bug, see comment #5. Do we need > to open a new update or is it possible to update the description ? > > Best regards, > Alex. Hello Alex, So this issue is not reproducible but a different one is ? Then I would close this one as RESOLVED WORKSFORME and open a new one...
(In reply to Alex ARNAUD from comment #8) > @Xisco: This bug description is outdated, there is always a mistake when a > paragraph on two pages but it's not the same bug, see comment #5. Do we need > to open a new update or is it possible to update the description ? > > Best regards, > Alex. I agree with you. @am_dxer, patrick, peter: could you please help us on this ? I don't have the needed time for this and I need your help. Best regards, Alex.
Hello, In order to help to reproduce this issue here are my revised steps. * Open the attached test case in LO Writer. * Look for line starting with "This is page 1" and verify if this is really the last line of a page. For some reason I had to delete an empty paragraph at the top in order to fix the test document. * Now position the caret at the begining of that line. * Start attached listener in a terminal and notice it has printed no output so far. * Move back to the LO window and press ctrl+right to jump right a word. * Now move to the terminal window and notice you can identify caret moved event * If identifying new output in a terminal window is difficult for you exit the listener by pressing ctrl+c and run it again. * Move to the LO window and press down, then up arrow key. * Go back to the terminal window and make sure you can identify both the caret moved events in the listener's output and you can also identify how LO reports you have moved into another paragraph during that move i.e. object:state-changed:focused event. * Now I believe you have understood what are we testing here so repeat it at the start of a line. * Compare your output with annotated output provided by @Joanmarie as a part of the bug description. My result: The issue is still present because when moving at the begining of a line object:state-changed:focused event is missing. If you are still unsure please do reread Joanies report until you can understand this better or ask again we can discuss it further if you need it. @Alex I can also reproduce what you are describing in comment 5 but I agree that's a different issue. So if we will end up creating another issue both of them are still reproducible and need fixing. My version string: Version: 6.2.1.2 Build ID: 6.2.1-1 CPU threads: 8; OS: Linux 5.0; UI render: default; VCL: gtk3; Locale: en-US (en); UI-Language: en-US Calc: threaded
Dear Joanmarie Diggs, 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
Hello, I can still reproduce this as explained in comment 11 with libreoffice 7.5.2. I am unable to copy the version of string from the Help -> About because of the different issue.