W3C home > Mailing lists > Public > public-canvas-api@w3.org > October to December 2011

Re: Request to re-open issue 131 -USE CASES, USE CASES, USE CASES

From: Jonas Sicking <jonas@sicking.cc>
Date: Tue, 20 Dec 2011 02:11:23 -0800
Message-ID: <CA+c2ei-H2co7a-tiAKq771L4wikN4gYyDMZaCg2b=THhOta_jA@mail.gmail.com>
To: Charles Pritchard <chuck@jumis.com>
Cc: Frank Olivier <Frank.Olivier@microsoft.com>, Richard Schwerdtfeger <schwer@us.ibm.com>, Steve Faulkner <faulkner.steve@gmail.com>, Cynthia Shelly <cyns@microsoft.com>, david bolter <david.bolter@gmail.com>, "dbolter@mozilla.com" <dbolter@mozilla.com>, Maciej Stachowiak <mjs@apple.com>, Paul Cotton <Paul.Cotton@microsoft.com>, "public-canvas-api@w3.org" <public-canvas-api@w3.org>, "public-html@w3.org" <public-html@w3.org>, "public-html-a11y@w3.org" <public-html-a11y@w3.org>, Sam Ruby <rubys@intertwingly.net>
On Mon, Dec 19, 2011 at 12:55 PM, Charles Pritchard <chuck@jumis.com> wrote:
> On this topic, I'm fine with the current specification and its
> scrollPathIntoView method. The method was authored shortly after the
> setCaretSelectionRect proposal, and though there may be some defects in the
> scroll into view mechanisms, those are something to be taken up with CSSOM.

Do we need scrollPathIntoView if we have a method for associating a
path with an element (i.e. "hit testing")? If we had that then it
would seem like simply calling scrollIntoView on that element should
do the trick.

/ Jonas
Received on Tuesday, 20 December 2011 10:14:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 20 December 2011 10:14:50 GMT