https://bugs.documentfoundation.org/show_bug.cgi?id=41063
--- Comment #40 from KDM <[email protected]> --- (In reply to sdc.blanco from comment #37) > Regression report in relation 4.4.7.2 > (+ important additional precision in bug report) > > For Version: 4.4.7.2 > Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600 > Windows 7 > > Test #1 > > 1. Cursor is placed on p. 1, but not in table > 2. Mouse Scroll to page 2 > 3. with both autosave or manual save: NO jumpback (i.e., screen remains on > p. 2) > > Test #2 (original bug report) > > 1. Cursor placed on p. 1, but IN table > 2. Mouse Scroll to page 2 - > 3. with both autosave or manual save: JUMPBACK to cursor on p. 1 > > > For Version: 5.1.2.2 > Build ID: d3bf12ecb743fc0d20e0be0c58ca359301eb705f > CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; > Locale: da-DK (da_DK) > > 1. Does not matter whether cursor is in table or in text on p.1, > > 2. Mouse scroll to page 2 > > 3. With both autosave and save, jumps back to the cursor on page 1 > (regardless of whether cursor was in table or text) > > Conclusion: > > 1. Original bug report was in relation to cursor in table. This problem > appears in both 4.4.7.2 and 5.1.2.2 (Windows) > > 2. So I agree that this behavior (with the cursor in the table) is not a > regression. > > 3. But there is a change/difference between 4.4.7.2 and 5.1.2.2 if the > cursor is NOT in a table. For 4.4.7.2, the save/autosave will leave the > screen view as it was. With 5.1.2.2, the save/autosave will return the > screen view of where the cursor was found. > > 4. I want to raise the hypothesis that some of the reports, after the > original bug report, may not have appreciated that the problem was reported > in relation to a cursor in a table! > > a. They may have been referring to the situation where the cursor was > NOT a table (i.e., a different situation). (this is noted explicitly in > comment 15) > b. In these cases, it seems that the screen view does change (at least > with 5.1.2.2), and many of the reports here seem to indicate that this > behavior started with 5.x series. (see comment 15 through comment 22 ) > c. Some think it should do that (comment 4) others do not (comment 12 > and comment 17 and others) > > 5. I will not make any changes here, but will leave the matter for QA folk > to make appropriate changes in the bugtracker (i.e., if a new bug report > should be created for the new situation). > > 6. Maybe the summary title of this bug should be changed to include the > words "cursor in the table" to make the matter clear. > > 7. Finally, I will remove this bug from the Autosave/Autorecovery meta bug, > because it not an issue with Autosave/Autorecovery This sums it up well. But while it's true that the original post was specific to text in tables (maybe NOT a regression but still a problem), others have opened bug reports about the issue when it involves text outside of tables and those bug reports have always been merged into this one. Thank you for helping to further clarify the issue. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
