Re: [w3c/webcomponents] Proposal: a native solution for virtual scrolling (#791)

@domenic I apologise, I thought my CSSOM proposal made it clear what I was
asking for. I even discussed the browser scroll height limits in the FAQ
section of my gist. I find it hard to believe that those limits are there
for no reason and can simply be lifted. Even if that were the case, virtual
scrolling in this way requires unnecessary boilerplate and hoop-jumping. It
is essentially a hack to do something that is otherwise not possible. What
I'm asking for, is a simple and purpose-built API that enables virtual
scrolling.

> The virtual scroller prototype so far is entirely layered on top of
low-level features, and uses no magic capabilities unavailable to web
developers, so it's unclear in what way you see it failing to meet its
goals.

Do you mean to say that the std:virtual-scrolled would be bound by the same
scroll height/width limits imposed by browsers, and wouldn't be optimised
to work off of low level scrollbar APIs? If that's the case, then I stand
corrected, but that seems like all the more reason to come up with
something better that virtual-scrolled can build on top of.

On Tue, 12 Feb 2019, 19:55 Domenic Denicola, <notifications@github.com>
wrote:

> @andyearnshaw <https://github.com/andyearnshaw> I'm kind of unclear what
> you're asking for. It seems like your main complaint is that some browsers
> have limits on scrollbar height that are lower than you'd like. That
> doesn't seem like a low-level primitive or API to me; it's just a limit
> you'd like lifted, similar to various other unspecified, browser-specific
> limits on the platform such as maximum string size, amount of memory used,
> etc. I think you'd be best served, if that is your real goal, by filing
> issues on browsers explaining how it'd be helpful for you to see that limit
> lifted.
>
> The virtual scroller prototype so far is entirely layered on top of
> low-level features, and uses no magic capabilities unavailable to web
> developers, so it's unclear in what way you see it failing to meet its
> goals.
>
> —
> You are receiving this because you were mentioned.
>
>
> Reply to this email directly, view it on GitHub
> <https://github.com/w3c/webcomponents/issues/791#issuecomment-462910121>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ABvdE24Rm5-muWRk89QgRIjUnNmywYcXks5vMxw_gaJpZM4avdLt>
> .
>


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/791#issuecomment-462963512