24748 2014-02-20 19:11:55 +0000 An event to notify the page that we're about to scroll (e.g. because a node was focused) 2014-03-11 16:56:20 +0000 1 1 1 Unclassified CSS CSSOM unspecified Other other NEW P3 normal --- 24750 1 ian zcorpan ian mike zcorpan public-css-bugzilla oldest_to_newest 100986 0 ian 2014-02-20 19:11:55 +0000 Use case: some fallback content in a canvas is given AT focus (not keyboard focus) and the user agent, based on an AT request, would like to scroll to the element. However it's being painted on a canvas, and in fact is off the canvas at this time, so we need to tell the author to scroll to it. Proposed design: whenever we need to scroll, fire an event on the element, that bubbles, and whose default action is to do the scroll. When the event is fired on a canvas or a fallback element in a canvas, include the relevant region, if any (much as we do with mouse events). 100987 1 ian 2014-02-20 19:12:12 +0000 zcorpan: Should this belong in CSSOM? 101228 2 zcorpan 2014-02-24 10:12:05 +0000 I'm OK with having this in CSSOM View, although I think it really belongs in "the" UI Events spec. Given the information in this bug I'm not confident with my ability to spec what is needed here, I have no idea what hooks, if any, you need for canvas. Maybe you can spec out in HTML what you have in mind first? 101248 3 ian 2014-02-24 18:27:13 +0000 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. 101320 4 zcorpan 2014-02-25 09:46:41 +0000 How about 'beforescroll'? So these cases should not fire it: User scrolls normally. Scrolling API is invoked. focus() is invoked. But these should (if scrolling is necessary): User asks for AT focus on some element. User asks for keyboard focus on some element (e.g. tabs to it). ? 102208 5 ian 2014-03-11 16:56:20 +0000 Sounds right.