Bug 89168 - android: React on page size changes
Summary: android: React on page size changes
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Android Viewer (show other bugs)
(earliest affected) Master
Hardware: Other All
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: mabAndroid
  Show dependency treegraph
Reported: 2015-02-06 12:19 UTC by Jan Holesovsky
Modified: 2021-01-18 04:08 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:
Regression By:

How it looks like currently. (28.34 KB, image/png)
2019-01-18 08:48 UTC, Miklos Vajna

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Holesovsky 2015-02-06 12:19:30 UTC
In the about dialog, choose 'Show Notice', and it opens, and shows all the content.

The problem is that it shows an additional empty page with few horizontal grey stripes, so it looks like if something went wrong, and the user should see something more, but does not.

Hopefully just means that we get wrong amout of pages from LibreOffice :-)
Comment 1 Christian Lohmaier 2015-10-03 20:04:57 UTC
works for me in current master
Comment 2 Jan Holesovsky 2015-10-08 08:23:50 UTC
I'm afraid there are still other documents that do not work correctly, as there is no implementation of the LOK_CALLBACK_DOCUMENT_SIZE_CHANGED handling; so let's keep it open please, just with a changed summary...
Comment 3 Xisco Faulí 2018-01-17 17:17:35 UTC
Hello Jan Holesovsky,
Is this issue still reproducible in master?
Comment 4 QA Administrators 2019-01-18 03:59:00 UTC Comment hidden (obsolete)
Comment 5 Miklos Vajna 2019-01-18 08:47:02 UTC
(In reply to Xisco Faulí from comment #3)
> Hello Jan Holesovsky,
> Is this issue still reproducible in master?

Yes, it is. Steps:

1) open a oneliner document
2) enable experimental mode to have editing
3) press enter enough times to have a second page

Expected: the second page shows up

Actual: the cursor goes outside the only page
Comment 6 Miklos Vajna 2019-01-18 08:48:06 UTC
Created attachment 148419 [details]
How it looks like currently.
Comment 7 QA Administrators 2021-01-18 04:08:22 UTC
Dear Jan Holesovsky,

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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team