- From: <bugzilla@jessica.w3.org>
- Date: Mon, 24 Feb 2014 18:27:13 +0000
- To: public-css-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24748
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|HTML |CSSOM
Assignee|ian@hixie.ch |simonp@opera.com
Product|WHATWG |CSS
Target Milestone|Unsorted |---
QA Contact|contributor@whatwg.org |public-css-bugzilla@w3.org
--- Comment #3 from Ian 'Hixie' Hickson <ian@hixie.ch> ---
I can take care of the canvas side of this the same way I do it for MouseEvent
(see "partial interface MouseEvent" in the HTML spec). I think we only need a
spec to say "when a user agent feels the need to scroll to a particular part of
the page, e.g. due to the user moving the focus or due to an accessibility tool
requesting a scroll to a specific element, the user agent must fire this event
and if it's not canceled must scroll to the element in question" (which then
fires a scroll event, of course). This would be distinct from regular scrolling
via the scrollbar, touch pan, or as the default action of a mouse wheel event.
Just make sure you use a new event type so that I can extend it.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 24 February 2014 18:27:15 UTC