Bug 155620 - Docx content can't be rendered completely on high resolution android device
Summary: Docx content can't be rendered completely on high resolution android device
Status: NEEDINFO
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Android Viewer (show other bugs)
Version:
(earliest affected)
7.6.0.0 alpha1+
Hardware: Other Android
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-06-01 08:47 UTC by disco
Modified: 2023-11-07 18:31 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
video of the bug (15.90 MB, application/octet-stream)
2023-06-01 09:05 UTC, disco
Details

Note You need to log in before you can comment on or make changes to this bug.
Description disco 2023-06-01 08:47:11 UTC
Description:
case1:
phone:android 9.0/resolution:2560*1440
when i use android viewer to display a docx file(this file only have 14 pages and 344kb),Only the first few pages are rendered(only front 5 pages)the rest not (only rendered empty white background).But when i scale the viewport to small(very small) it's rendered

case2:
phone:the same with above but change its resolution to:1920*1080
the docx file was rendered completely and everything is ok

Steps to Reproduce:
1.change the phone resolution to 2560*1440 or higher
2.use android viewer open the docx


Actual Results:
Only the first few pages are rendered when scrolling

Expected Results:
all page should be rendered when scrolling


Reproducible: Always


User Profile Reset: No

Additional Info:
the docx file contain chinese and few images
Comment 1 disco 2023-06-01 09:05:04 UTC
Created attachment 187635 [details]
video of the bug
Comment 2 disco 2023-06-02 08:56:06 UTC
I found this problem is caused by high dpi(>=640)
Comment 3 Michael Weghorn 2023-06-03 15:12:27 UTC
Thank you for your report.

Can you please attach the sample file with which you encounter this issue? (And then set the status back to UNCONFIRMED. Confirming the bug by setting the status to NEW should be done by somebody else then the bug reporter; it means that somebody else was able to reproduce the issue.)
Comment 4 disco 2023-06-16 01:27:20 UTC
for some reason i can't attach the sample file,but i can provide some information about the sample file. It's normal text on the first few pages but the rest is  a lot of images
Comment 5 Michael Weghorn 2023-06-19 11:50:00 UTC
(In reply to disco from comment #4)
> for some reason i can't attach the sample file,but i can provide some
> information about the sample file. It's normal text on the first few pages
> but the rest is  a lot of images

Probably the file exceeds the maximum file size for attachments. Can you try to either upload the file to somewhere else and share a link here or simplify the file (e.g. remove some pages while still keeping the problem reproducible)?
Comment 6 disco 2023-06-21 02:23:07 UTC
(In reply to Michael Weghorn from comment #5)
> (In reply to disco from comment #4)
> > for some reason i can't attach the sample file,but i can provide some
> > information about the sample file. It's normal text on the first few pages
> > but the rest is  a lot of images
> 
> Probably the file exceeds the maximum file size for attachments. Can you try
> to either upload the file to somewhere else and share a link here or
> simplify the file (e.g. remove some pages while still keeping the problem
> reproducible)?

It's not a technical reason but for security(the sample file has some privacy information that can't be exposed)
Comment 7 QA Administrators 2023-06-21 03:14:10 UTC
[Automated Action] NeedInfo-To-Unconfirmed
Comment 8 Michael Weghorn 2023-06-21 14:38:04 UTC
(In reply to disco from comment #6)
> It's not a technical reason but for security(the sample file has some
> privacy information that can't be exposed)

Can you possibly try whether you can create a new file that just has dummy text (like "Lorem ipsum ...") and non-confidential pictures to see whether that shows the same issue?