Created attachment 149493 [details]
Selecting "hide whitespace" or "view web" cause the view position to constantly jump until the entire document has been processed.
This prevents viewing and editing the document until the reformatting process completes. My screen grab shows a 95 page document that takes around 7 seconds before the view stabilizes. Warning, trying this on a large document may result in seizure and/or death.
* Open a document of more than 50 pages
* Select "view | hide whitespace"
* Using the navigator, jump to a position near the end of the document
I can't confirm this with a document of 93 pages and
Version: 126.96.36.199 (x64)
CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard;
Gebietsschema: de-DE (de_DE); Calc: group threaded
(In reply to Dieter Praas from comment #1)
> I can't confirm this with a document of 93 pages and
> Version: 188.8.131.52 (x64)
> Build-ID: 90f8dcf33c87b3705e78202e3df5142b201bd805
> CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard;
> Gebietsschema: de-DE (de_DE); Calc: group threaded
Running on windows 10.0.17763
Document has a large number of small tables in case that is causing the problem
Created attachment 149499 [details]
Doc that causes jitter
The attached file causes the problem on my PC
(In reply to matt from comment #3)
> Created attachment 149499 [details]
> Doc that causes jitter
> The attached file causes the problem on my PC
I also couldn't reproduce the bug with your document
The attached screen video clearly shows the bug. If not, what more do you need?
I'm unclear why you've left this with a status of unconfirmed. You have not requested additional information and didn't share what platform and hardware you used to reproduce the bug. I'm unclear on how to move forward resolving this.
If you guys have more bugs than you can resolve, it would helpful if you'd share that with the community so we don't waste our and your time posting bugs you don't have bandwidth to resolve.
(In reply to matt from comment #5)
> The attached screen video clearly shows the bug.
Yes I saw it
> I'm unclear why you've left this with a status of unconfirmed.
The status is UNCONIRMED until anybody else than th bug reporter is able to reproduce the bug. As I wrote in comment 1, I'm not able to reproduce the bug.
> I'm unclear on how to move forward
> resolving this.
Perhaps somebody else can confirm it.
> If you guys have more bugs than you can resolve, it would helpful if you'd
> share that with the community so we don't waste our and your time posting
> bugs you don't have bandwidth to resolve.
Yes there are a lot of open bugs, and peolpe who want to help are welcome. I'm just e normal user and spent free time to help to improve LO.
Thank you for reporting the bug. I can reproduce this bug, but not all the time.
1.) First time - I Select "hide whitespace" and use navigator to jump to the last position, there is no jump.
2.) Second time - I deselect "hide whitespace" and again select "hide whitespace" and use navigator to jump to the last position, there is no jump.
3.) Third time - Now again, I deselect "hide whitespace" and again select "hide whitespace" and use navigator to jump to the last position, here there is a jump.The view position jump until the entire document has been processed
So there is a jump every third time I repeat these steps.
Build ID: b6b28931435e44aca92b8c0e1659f701e3ed1a87
CPU threads: 2; OS: Windows 6.1; UI render: default; VCL: win;
TinderBox: Win-x86@42, Branch:master, Time: 2019-01-30_06:57:04
Locale: en-US (en_US); UI-Language: en-US
It seems to be more noticeable with hide whitespace than web view. On Linux, I get the jitter on the first try with hide whitespace, but with web view I don't notice anything.
Hide whitespace is not an ancient feature, so we can't regression test with the oldest versions. With 3.3.0, 3.5.0 and 4.3.0 on Win 10, web view does not exhibit any strangeness.
An unfortunate thing is that the problem (with Hide whitespace) is not seen in the latest commit of win32-5.4 bibisect repo, but already seen in the oldest commit of win32-6.0.
The problem is seen in release build 5.4.2.
Let's add a bibisect request so someone else can try.
Arch Linux 64-bit
Build ID: e967aea2d8cc4f9fc608cb726cb474c184fb61de
CPU threads: 8; OS: Linux 5.0; UI render: default; VCL: gtk3;
Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US
Built on 7 April 2019
I can not reproduce with Version: 184.108.40.206.alpha0+
Build ID: 31ac398cfa30694b18240d31df17a58d699b5bf6
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3;