Proposal: Exposing native scroll as API

Andy Earnshaw andyearnshaw at gmail.com
Mon Jun 24 09:51:38 UTC 2019


As Claude pointed out, Scrolling is not part of ECMAScript. On the subject
of improved support for virtual scrolling, I've started discussions on
CSS-WG and Web Components issue trackers.

https://github.com/w3c/csswg-drafts/issues/3397
https://github.com/w3c/webcomponents/issues/791

Please feel free to add your +1 there or contribute your own use cases to
the discussion.

On Sat, 22 Jun 2019 at 19:41, kai zhu <kaizhu256 at gmail.com> wrote:

> the referenced video was entertaining to watch (and i learned new things
> about typescript and proxies), but i still don't understand your UX-problem
> -- at least enough to know what/how a new standard-api would help.
>
> there's a bunch of canvas-scrolling examples @
> https://konvajs.org/docs/sandbox/Canvas_Scrolling.html.  examples #1 and
> #4 implement native canvas-scrolling, with the latter having less jankiness
> on my mobile-chrome.  maybe you're asking for consistent #4 css-behavior
> across all mobile-browsers (i have no idea if it works as well in
> ios-safari)?  that would be w3c csswg's domain.
>
> also somewhat-related -- chrome is debating an intent-to-implement feature
> for scrollTo-behavior for text-fragments.
> for example:
> `https://www.example.com#targetText=You%20may%20use%20this%20domain`
> <https://www.example.com#targetText=You%20may%20use%20this%20domain>
> will scroll to element in www.example.com containing text "You may use
> this domain". [1]
>
> [1] Scroll-To-Text using a URL fragment
> https://github.com/bokand/ScrollToTextFragment
>
>
> On Fri, Jun 21, 2019 at 10:33 AM 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
>>
> _______________________________________________
> 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/20190624/80cee2a2/attachment.html>


More information about the es-discuss mailing list