- From: <bugzilla@jessica.w3.org>
- Date: Tue, 27 Jan 2015 23:57:40 +0000
- To: public-html-admin@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27913
Bug ID: 27913
Summary: focusing steps don't contain scrolling an element into
view
Product: HTML WG
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: HTML5 spec
Assignee: dave.null@w3.org
Reporter: mail@rodneyrehm.de
QA Contact: public-html-bugzilla@w3.org
CC: mike@w3.org, public-html-admin@w3.org,
public-html-wg-issue-tracking@w3.org
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.
[1] http://dev.w3.org/csswg/cssom-view/#scroll-an-element-into-view
[2] http://www.w3.org/html/wg/drafts/html/master/editing.html#focusing-steps
[3]
http://www.w3.org/html/wg/drafts/html/master/editing.html#focus-management-apis
--
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 27 January 2015 23:57:44 UTC