Problem description: Steps to reproduce: 1. Make cell with many lines of text in it(not fit in one screen by height) 2. Try to scroll to end of text Current behavior: You don't view and of cell. After try to scrol to end of cell you see next cell, so no way to see part of content not fit in one page. Expected behavior: On scroll big cell scroll cell to end before switch to next cell Operating System: Windows 7 Version: 4.1.1.2 release
Reproduced with LibO 4.1.2.3 on Win7. A precision : after "Try to scroll to end of text", add "with the main panel right scrollbar" ; the scroll in the formula field is OK, it permits to see the end of big cells content, one at a time. About the proposed "expected behavior" : to deal with very very big contents, I propose the rewording "On big cell scroll, before switching to next cell, scroll cell to next vertical hidden slice of data". Why not the same proposal along the horizontal axis (pb probably more frequent) ? In any case, that involves the ability to go beyond the current characteristic "always the left-high corner of a cell at the left-high corner of the main grid". Some thinking of the consequence still to conduct. IMHO enhancement.
Please attach a test document where we can see this problem so we are sure we're seeing the same issue. Marking as NEEDINFO - once an attachment is added mark as UNCONFIRMED and we'll go from there. Thanks!
Dear Bug Submitter, 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 INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/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 Message generated on: 2015-02-18
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID 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 -- The LibreOffice QA Team This NEEDINFO Message was generated on: 2015-04-01 Warm Regards, QA Team
Created attachment 138567 [details] A spreadsheet doc with merged cells big enough to really "feel" the problem. I can confirm that this issue is still here. See the linked file features merged cells that block the scrolling until the user has scrolled enough for the view to change. Come on, you're about to update LO version number to 6. I've been testing the beta and this annoyance is still something we have to deal with, while most other spreadsheets are using smooth scrolling for a while now.
You can reproduce it on mac, linux and windows (I've tested on 7 and 10), with a mouse or a trackpad, no difference. It most certainly has to do with the way Calc handles the view.
*** This bug has been marked as a duplicate of bug 34689 ***