Open
Bug 519609
Opened 15 years ago
Updated 2 years ago
Click events are not registered on the right (or left) edge of a scrollbar when using a GTK theme with a trough-border greater than zero.
Categories
(Core :: Widget: Gtk, defect, P5)
Tracking
()
UNCONFIRMED
People
(Reporter: erappleman, Unassigned)
References
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4pre) Gecko/20090929 Ubuntu/9.10 (karmic) Firefox/3.5.4pre
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4pre) Gecko/20090929 Ubuntu/9.10 (karmic) Firefox/3.5.4pre
See the following for more information.
https://bugs.launchpad.net/ubuntu/+source/human-theme/+bug/422511
http://bugzilla.mozilla.org/show_bug.cgi?id=486065
Reproducible: Always
Reporter | ||
Updated•15 years ago
|
Summary: Click events are not registered on the right edge of a scrollbar when using a GTK theme with a trough-border greater than zero. → Click events are not registered on the right (or left) edge of a scrollbar when using a GTK theme with a trough-border greater than zero.
Reporter | ||
Comment 1•15 years ago
|
||
Also consult this must-read:
https://bugs.edge.launchpad.net/ubuntu/+source/xulrunner-1.9.1/+bug/327863/
Updated•15 years ago
|
Component: General → Widget: Gtk
Product: Firefox → Core
QA Contact: general → gtk
Please see my comments in bug 525224.
I'll quote the important usability comment:
"There's a reason the Back button doesn't have an unclickable area to the left.
It allows you to hammer your mouse over to the left of the screen and be sure
you're hitting the Back button.
The same usability principles apply everywhere. If you take a look at various
themes (charamel, [silvermel]) you'll notice the vertical scroll bar does not has an unclickable/unscrollable border to it. You can hammer your mouse over to the right and be sure you're able to scroll. Who would want to target their mouse to a specific ~20px region?"
(linux, x86_64, firefox 3.5.4, stock theme)
See Also: → https://launchpad.net/bugs/422511
Comment 5•14 years ago
|
||
Are there any CSS workarounds for this? None of my attempts so far have yielded a viable solution.
Comment 6•5 years ago
|
||
Priority: -- → P5
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•