This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 27913 - focusing steps don't contain scrolling an element into view
Summary: focusing steps don't contain scrolling an element into view
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML a11y Task Force (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Charles McCathieNevile
QA Contact: This bug has no owner yet - up for the taking
Keywords: a11y_focus
Depends on:
Reported: 2015-01-27 23:57 UTC by Rodney Rehm
Modified: 2016-04-28 16:08 UTC (History)
7 users (show)

See Also:


Description Rodney Rehm 2015-01-27 23:57:40 UTC
All browsers scroll an element into view [1] upon the element gaining focus [2]. Of course they behave differently in doing so (varying scroll to top, bottom, center).

Can we have this scrolling step formally defined so user agents might eventually behave the same way?

I'd also like to mention that this scrolling behavior can currently *not* be prevented. When CSS Transitions and CSS Animations are used to reveal the focus target, authors have to wait for the transition to finish before setting focus. If they don't wait, content is at risk of being scrolled by the user agent, effectively messing up any complex UI. It would go a long way if we could extend Element.focus [3] in a way that prevents this native scrolling.

Comment 1 Charles McCathieNevile 2015-01-28 00:06:43 UTC
I think this might be a duplicate of an existing bug, but I don't have time to check yet. Adding it to the list in the hopes that I do so soon :)
Comment 2 Charles McCathieNevile 2015-07-10 22:33:32 UTC
Is this a duplicate of 16186?
Comment 3 Rodney Rehm 2015-07-10 23:12:19 UTC
I don't believe this is a duplicate of 16186 per se - although the issues seem closely related.

Bug 16186 is looking at things based on document navigation, i.e. in response to the document's URL fragment changing. From what I understand, focusing a particular element does not equate to navigating the document. I may be mistaken and this may actually be the same thing, in which case this bug is to be considered a duplicate of 16186 - with the addition of asking for a way to prevent or delay the scrolling.
Comment 4 Rodney Rehm 2015-09-03 13:04:09 UTC
bug was copied to whatwg/html -
Comment 5 LĂ©onie Watson 2016-04-28 16:08:30 UTC
Moved to HTML on Github: