W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2012

Re: [whatwg] Should scrollbars move focus?

From: Etienne Levesque Guitard <etiennelg@gmail.com>
Date: Fri, 2 Nov 2012 09:21:49 -0400
Message-ID: <CADJPd87fatC=od7wbev60cHcTbQE=VMV_6O5e+32TDB3BHEzkg@mail.gmail.com>
To: James Ross <silver@warwickcompsoc.co.uk>
Cc: WHATWG <whatwg@lists.whatwg.org>
Wouldn't this be considered a browser-specific  implementation
bug/inconsistency then?

It seems that it's done because the scrollbars have to be in the DOM, and
therefore act as elements in the DOM tree (clicking in a random div for
instance does change focus, so the implementation is correct in the sense
of HTML). However, it doesn't look like this ever was looked at. It's just
the bi-product of the way the DOM is typically implemented.

Shouldn't it be fixed? Or rather, can it without breaking DOM functionality
in the browser?
On 2012-11-02 8:02 AM, "James Ross" <silver@warwickcompsoc.co.uk> wrote:

> > From: ojan@chromium.org
> > Date: Thu, 1 Nov 2012 10:45:07 -0700
> >
> > I didn't test nested scrollbars in Windows. I believe Elliott may have. I
> > did test them on Mac and Ubuntu. Clicking on nested scrollbars doesn't
> move
> > focus even if the scrollable element is focusable. On Ubuntu, clicking on
> > scrollbars doesn't even change window focus if the scrollbar is in a
> > different window.
>
> On Windows (tested on 7 using the Resource Monitor and Command Prompt
> properties windows), interacting with scrollbars will focus the window, but
> not the scrollable item itself (i.e. preserving the focus within the
> window).
>
> However, Internet Explorer (9, on Windows 7), will move the focus to the
> scrollable element (for all types in Robert's test page).
>
> James
Received on Friday, 2 November 2012 13:22:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 January 2013 18:48:11 GMT