Description: I think screen rendering is the correct term, but despite having a 4k display and a high spec graphics card, I am having problems when paging up and down a 4 page document. It contains two tables and roughly ten paragraphs, saved as a docx as it will be shared, but using page up/down causes severe disruption to the viewing of the document with parts of it not being visible. Steps to Reproduce: 1.Page Up 2.Page Down 3. Actual Results: incorrect display of a document as if using a very old, slow graphics card when the opposite is true. Expected Results: smooth rendering and perfect view of the document. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.2.1.2 (x64) / LibreOffice Community Build ID: 87b77fad49947c1441b67c559c339af8f3517e22 CPU threads: 16; OS: Windows 10.0 Build 19043; UI render: Skia/Vulkan; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: CL
I have tried to take a screen capture of this issue happening with a non confidential document, but the problem corrects itself after a few seconds, not giving me time. I am a new user as I got tired of Microsoft Word, and having cerebral palsy, I was really missing the old drop-down menus, so would like to thank you all. Sarah PS.Please, please, never go down the road of thin scroll bars with no clickable arrows. They are the first ever accessibility nightmare to be allowed in Windows, presumably because did it in 10.7
(In reply to Sarah from comment #1) > I have tried to take a screen capture of this issue happening with a non > confidential document, but the problem corrects itself after a few seconds, > not giving me time. So can we close this one?
No, please don't close it. The problem is both severe and disruptive. It definitely needs to be addressed. Sarah
This report is a general one, but not specific and reproducible so not confirmed. So I guess there are prior reports, from meta bug 98754 and so on. But let's see. Please search existing bugs, you may use some attachment, and attach a screencast of what you see (with Camstudio or ShareX or else). You commented in bug 134324 and it may really be the same, but that one is with images, you mention only tables and saving as DOCX. Are you saying that it becomes slow only if saved and reopened as DOCX?
Dear Sarah, 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 Sarah, 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