Bug 148636 - Layout of large Web documents makes some (large) parts of text stay "between" pages
Summary: Layout of large Web documents makes some (large) parts of text stay "between"...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer Web (show other bugs)
Version:
(earliest affected)
7.2.0.0.alpha0+
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, regression
Depends on:
Blocks: Writer-Web-Layout
  Show dependency treegraph
 
Reported: 2022-04-17 11:19 UTC by Mike Kaganski
Modified: 2025-02-22 03:11 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Screenshot of the problem (118.96 KB, image/png)
2022-04-17 11:19 UTC, Mike Kaganski
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Kaganski 2022-04-17 11:19:12 UTC
Created attachment 179625 [details]
Screenshot of the problem

1. Open Help->License Information->Show License.
2. Wait for repagination (page count in the status bar) to settle down.
3. Go to page 2 (click on the page number in the status bar, and enter "2" in the Go to Page dialog).

The top of the second page shows some garbage. Selecting from the last line of page 1 to the first part of page 2, copying to clipboard and pasting to a text editor shows that there are several lines in the clipboard between the two (partially) visible on screen.

This is not consistent, and depends on the window size; making the window not full-screen, and then making it full-screen again, makes it fix itself. It might be visible on other pages, not only between p1 and p2; it may be not visible on read-only view, but appear when you open it for editing.

I was able to bibisect it to commit 0fedac18214a6025401c4c426466a5166553e8ec
  Author Luke Deller <luke@deller.id.au>
  Date   Fri Apr 09 09:08:37 2021 +1000
    tdf#141556 Fix 100% CPU usage in Writer idle loop
Comment 1 Stéphane Guillou (stragu) 2022-09-09 20:28:29 UTC
I can't reproduce in:

Version: 7.2.7.2 / LibreOffice Community
Build ID: 8d71d29d553c0f7dcbfa38fbfda25ee34cce99a2
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

nor with:

Version: 7.5.0.0.alpha0+ / LibreOffice Community
Build ID: 24087697d5cf78aac346d4dcea0596373e15a95c
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

Mike, could you test again? Or maybe it's Windows-specific?
Comment 2 Mike Kaganski 2022-09-10 11:25:40 UTC
Repro using Version: 7.4.1.1 (x64) / LibreOffice Community
Build ID: 0a046a10cbf1679eea5538bd3ab63156caa3a036
CPU threads: 12; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: ru-RU (ru_RU); UI: en-US
Calc: CL
Comment 3 Stéphane Guillou (stragu) 2022-12-20 14:07:58 UTC
Was able to reproduce on Windows 10:

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 9b46020c262045aed0beace4708565235c2523cc
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: en-GB (en_GB); UI: en-GB
Calc: threaded

Also reproducible without Skia:

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 9b46020c262045aed0beace4708565235c2523cc
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: default; VCL: win
Locale: en-GB (en_GB); UI: en-GB
Calc: threaded
Comment 4 QA Administrators 2025-02-22 03:11:41 UTC
Dear Mike Kaganski,

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