Issue 89149 - Main vertical scroll bars do not respond at screen edge
Summary: Main vertical scroll bars do not respond at screen edge
Status: CLOSED DUPLICATE of issue 123007
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: DEV300m9
Hardware: PC Windows Vista
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2008-05-08 01:36 UTC by moreati
Modified: 2017-05-20 10:01 UTC (History)
2 users (show)

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


Note You need to log in before you can comment on or make changes to this issue.
Description moreati 2008-05-08 01:36:54 UTC
When Impress, Calc, Write or Draw are maximised it is not possible to use the
vertical scroll bar at the very edge of the screen. There is dead space in which
the scroll bar does not respond to mouse clicks. According to Fitts Law, it is
much easier for the user to click on something at the screen edge rather than a
few pixels away from the edge.

This affects 2.4 and 3.0 beta on Windows Vista. Notepad exhibits the same
behaviour, so this may be due to the native widget. However Firefox scroll bars
are clickable all the way to the edge. I will test on Ubuntu/Gnome and update
this bug.
Comment 1 moreati 2008-05-08 11:18:24 UTC
Behaviour is the same on Ubuntu 8.04 with 2.4 under Gnome, with default
GTK theme. Scroll bar is inset from screen edge by 2 or 3 pixels when Writer is
Comment 2 conte4313 2009-03-27 03:50:20 UTC
I have Vista x64 using 3.0 and it's the same here. 

I completely agree with you about this design flaw and it would indeed allow
users to select the scroll bar faster and with less error, since the cursor
doesn't move past the screen. Many other applications allow this, including 5
different web browsers I've tried (except Internet Explorer).

This seems like a very simple fix which wouldn't affect the overall
functionality of any Open Office applications, which is probably why of little
priority since there are probably more bigger concerns but it should still be
Comment 3 Edwin Sharp 2014-02-05 14:01:56 UTC
Duplicate bug

*** This issue has been marked as a duplicate of issue 123007 ***