Description: In essence the same as bug 41063, however without complexity of the auto-save. Steps to Reproduce: 1. Open the attached file 2. Zoom in; de second page shouldn't be visible 3. Make sure that the cursor is at the top of the table 4. Scroll down to the bottom of the second page (without a change to the cursor) 5. Press add a row below Actual Results: Screen jumps back to the cursor position Expected Results: Depending on the opinion of bug 115781. *Cursor & screen position should jump to the new row; or *Screen position should stay the same Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/603.3.8 (KHTML, like Gecko) Version/10.1.2 Safari/603.3.8
Created attachment 140083 [details] example
Reproducible with Version: 6.1.0.0.alpha0+ (x64) Build ID: 77a535285f0fd5f2464430abdc67cf99be024868 CPU threads: 4; OS: Windows 10.0; UI render: GL; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-01-23_23:04:23 Locale: de-DE (de_DE); Calc: CL
@Justin You did attempt to fix the "Saving while in table causes view to jump to cursor position" a while ago. However, drowning because of the progressbar (Bug 41063 comment 57). This looks like the same bug, without all the saving complexity ;-). I thought you might be interested..
(In reply to Telesto from comment #3) > @Justin > thought you might be interested.. Justin, can you help with this bug?
(In reply to Dieter from comment #4) > (In reply to Telesto from comment #3) > > @Justin > > thought you might be interested.. > > Justin, can you help with this bug? Warning.. there are more cases.. and the assessment about the need to block the jump to cursor sometimes matter of taste/opinion/argument Where Mike says, the change changing to cursor making sense.. while I'm kind of disagreeing (or lacking the insight of the scope of the change). So this topic includes own assessments of the matter ;-)
Dear Telesto, 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
Still reproducible with Version: 7.5.0.1 (X86_64) / LibreOffice Community Build ID: 77cd3d7ad4445740a0c6cf977992dafd8ebad8df CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL threaded But taking into account bug 115781 (espacially comment 6) I would close it as WF or as duplicate of bug 115781, because I don't see the fundamental difference. Telesto, could you please explain? Heiko, do youthink, it's a duplicate or a WF? cc: Heiko Tietze
Bug 115781 was about to move the caret to the added row/column and we rejected this. This ticket is about the view port and any modification to the document, typing or inserting, should scroll back. In fact, if I scroll down and add a row, the view moves back to the position of the caret.
Dear Telesto, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Telesto, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp