Proposal: Exposing native scroll as API

guest271314 guest271314 at gmail.com
Fri Jun 21 23:06:04 UTC 2019


What are you NOT able to output right now relevant to programmatically
scrolling using existing DOM methods, Web Animations API, and/or CSS? Have
you filed an issue at browsers, WHATWG HTML, and WHATWG DOM?

On Fri, Jun 21, 2019 at 3:33 PM Adam Eisenreich <akxe at seznam.cz> wrote:

> If you want to have native scrolling experience for `<canvas>` you need to
> either implement your own scrolling behaviour, or you will create
> `<canvas>` of size much bigger than screen, that way it overflows screen
> and shows scollbars, but then you must only render on part of canvas as
> most is hidden.
>
> I would like an API I would ask:
> If this element **would be scrollable**, when scrolling would actually
> occur? How long would the animation take on this platform? Where the end
> offset would be?
> Scrolling isn't same for each platform ex.: PC, Mac, iOS, Android.
>
> There is video about proxx, it mentions other problems too, but they
> explain there how they did implement natural scrolling for `<canvas>`:
> https://youtu.be/ViyTYEv9dM8?t=1005
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20190621/06144c21/attachment.html>


More information about the es-discuss mailing list