Created attachment 152054 [details] Screencast showing the issue Version: 6.4.0.0.alpha0+ Build ID: 58a095ac31b9db967fa4529f5d072e0d01e32f33 CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded Steps to reproduce: 1) start Writer 2) open in Firefox: https://en.cppreference.com/w/cpp/language/copy_assignment 3) select all webite content (Ctrl+A), copy (Ctrl+C) 4) switch to Writer window, paste (Ctrl+V) Result: * document is displayed strangely * scrolling doesn't really work and makes the display even worse Further notes: * The behaviour is similar when using the kde5 VCL plugin instead of gtk3. * This works fine with libreoffice-6-2 branch. * Tested Debian testing, with KDE Plasma (X11) * The behaviour is also/still strange when opening the document after saving.
Created attachment 152055 [details] sample document after saving Attached is the document after saving. Opening the document in writer, it looks OK at first. However, when scrolling down all the way to the bottom, the scrollbar does goto the bottom, but bottom of page 3 i still shown in the document view. (This may be totally unrelated to the initial report though; I'll open a separate issue if this remains once the other one is fixed.)
Created attachment 152056 [details] Screenshot after trying to scroll down to the bottom The screenshot shows that the scrollbar at the right hand side is at the bottom, while the "middle" of the document is still shown.
confirm with Version: 6.4.0.0.alpha0+ Build ID: ce70dfe2ba577b3c49363c7218e4519611335edb CPU threads: 8; OS: Linux 4.19; UI render: default; VCL: gtk3; Locale: nl-BE (en_US.UTF-8); UI-Language: en-US Calc: threaded Version: 6.4.0.0.alpha0+ Build ID: ce70dfe2ba577b3c49363c7218e4519611335edb CPU threads: 8; OS: Linux 4.19; UI render: default; VCL: qt5; Locale: nl-BE (en_US.UTF-8); UI-Language: en-US Calc: threaded
Hi Michael, Looking at the screencast, it seems like a regression from a46a257794f1f53b294735fc876c394be23a3811, which got reverted in 76c4ed30437125a922936c036a3dc57441938c61. Could you please try again with a recent master version ?
For me it working Version: 6.4.0.0.alpha0+ Build ID: adcb7bacb452dccde70b20a902f5c1f23f37913f CPU threads: 8; OS: Linux 4.19; UI render: default; VCL: gtk3; Locale: nl-BE (en_US.UTF-8); UI-Language: en-US Calc: threaded Version: 6.4.0.0.alpha0+ Build ID: adcb7bacb452dccde70b20a902f5c1f23f37913f CPU threads: 8; OS: Linux 4.19; UI render: default; VCL: qt5; Locale: nl-BE (en_US.UTF-8); UI-Language: en-US Calc: threaded
(In reply to Xisco Faulí from comment #4) > Hi Michael, > Looking at the screencast, it seems like a regression from > a46a257794f1f53b294735fc876c394be23a3811, which got reverted in > 76c4ed30437125a922936c036a3dc57441938c61. > Could you please try again with a recent master version ? Yes, thanks, it (both, the initial report and what is mentioned in comment 1) works fine again with Version: 6.4.0.0.alpha0+ Build ID: 4a478227f5af8322164ecce66fd056e9bf2eac89 CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: kde5; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded
(When closing bugs, if we don’t know the exact commit fixing an issue, we don’t use FIXED but WORKSFORME)
See comment 4