Issue 94061 - The Zoom slider is cut off first when Writer window is shrinked
Summary: The Zoom slider is cut off first when Writer window is shrinked
Status: CONFIRMED
Alias: None
Product: Writer
Classification: Application
Component: viewing (show other issues)
Version: OOO300m5
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-19 07:17 UTC by dgillham25
Modified: 2019-07-11 14:44 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description dgillham25 2008-09-19 07:17:27 UTC 
I have a comment about the status bar on OpenOffice 3.0.
It does not fit in the window properly on my office computer.  I can only see
half of the percent box next to the zoom slider.  The rest of that box is cut
off.  The rest of Writer's window fits fine.
However, on my home computer, with a better resolution, the status bar is fine.
I though you should be made aware of this problem.
Test it on a monitor with a lower resolution setting.
Thank you.
Comment 1 michael.ruess 2008-10-20 17:51:23 UTC 
Reassigned to SBA.
Comment 2 stefan.baltzer 2008-10-29 19:14:46 UTC 
SBA: Confirmed. All OS and platforms. Adjusting fields.

Another scenario: 
 - When shrinking the window width, the Zoom slider will "vanish" first.
 -> Although there is "unused" or "less important" items in the status bar

I think that when shrinking a window, the Zoom slider shall be the "last thing"
to vanish. Adjusting summary to reflect the findings. 

Proposal: Think of a "vanish order" for the status bar items.

SBA->FME: For you or for PB? Please proceed, thx.
Comment 3 frank.meies 2008-10-30 09:08:21 UTC 
fme->sba: AFAIK, there's a system requirement of a resolution of at least
1024x768. With this resolution, the zoom slider is fully visible, we checked
this in the iTeam ;-) So I'm not sure if we really want to resolve this
'defect'. I suggest you talk to some of the framework UI gurus if they can/want
to have a look.