W3C home > Mailing lists > Public > www-style@w3.org > November 2013

Re: [css4-ui] [css-ui] Effect of pointer-events:none on scrollbars

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Tue, 19 Nov 2013 08:30:30 -0800
Message-ID: <CAAWBYDAnnyt8NfJsy12xzaWdA4zy13rAcPFLNmE+tBmP1mFhLg@mail.gmail.com>
To: Daniel Trebbien <dtrebbien@gmail.com>
Cc: WWW Style <www-style@w3.org>
On Tue, Nov 19, 2013 at 4:59 AM, Daniel Trebbien <dtrebbien@gmail.com> wrote:
> Hello,
>
> In working on a patch (https://codereview.chromium.org/68243009/) for Chrome
> Issue 313908 (http://crbug.com/313908), an issue has come up concerning the
> effect of pointer-events:none on overflow controls such as overflow
> scrollbars.
[...]
> Personally I think that IE 11's behavior makes better sense here because
> it's consistent that pointer-events:none on div2 prevents it from being
> scrolled.  In Firefox, if using overflow scrollbars, then it is possible to
> scroll div2.  However, if using overlay scrollbars, (e.g. Mac's "Show scroll
> bars" setting is changed to "When scrolling") then it is not possible to
> scroll div2.  Also, I think that fantasai's pointer-events:none analogy of
> an empty-set geometry points to IE 11's behavior as correct in this case.
> Furthermore, the fact that overflow scrollbars are rendered within the
> border-box of div2 (as can be seen by adding a border to div2), and the spec
> for pointer-events:visible mentions that an element may be the target of an
> event if over the borders, this conceptually implies that the overflow
> controls within the border-box are subject to the effect of pointer-events
> as well.
>
> Could the pointer-events spec be clarified on this issue?

I agree, IE's behavior seems to make more sense.

~TJ
Received on Tuesday, 19 November 2013 16:31:18 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:37 UTC