Closed Bug 880671 Opened 11 years ago Closed 11 years ago

unclickable scrollbar using overflow auto and pointer-events none

Categories

(Core :: DOM: UI Events & Focus Handling, defect)

21 Branch
x86_64
Windows Vista
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla25

People

(Reporter: cka, Assigned: spohl)

References

()

Details

User Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:20.0) Gecko/20100101 Firefox/20.0 (Beta/Release)
Build ID: 20130409194949

Steps to reproduce:

check http://jsfiddle.net/NczQG/2/
click on scrollbar in the output box
try to drag the handle
click on scrollbar arrows


Actual results:

nothing, the scrollbar does not react to my clicks


Expected results:

scrollbar and content should have reacted to my clicks.
Component: Untriaged → DOM: Events
Product: Firefox → Core
Component: DOM: Events → Event Handling
Why should the scrollbar respond to clicks in this testcase? It belongs to an element which is pointer-events:none. This bug looks invalid to me.
because the user expects it to react.
either the scrollbar is here and the user can interact with it, or it should not be here.

we cannot set pointer-events on the scrollbar under firefox, so we can't "fix it"
If you don't want the scrollbar to appear, make the element overflow:hidden.
sorry about the delay.
I do want the scrollbar to appear, but i still want clicks on content to fall through to other content below it.
Is this fixed in nightly builds for you on Windows? I think http://hg.mozilla.org/mozilla-central/rev/f8bf18dceb1c might have fixed it.
yes ! it's fixed ! thanks a lot.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Assignee: nobody → spohl.mozilla.bugs
Depends on: 891136
Target Milestone: --- → mozilla25
Component: Event Handling → User events and focus handling

Has this been un-fixed?
Cannot drag scollbar with the mouse using above Jsfiddle :(
Any solution or alternative to keep background content clickable AND be able to drag the scrollbar?

See Also: → 1839481
You need to log in before you can comment on or make changes to this bug.