You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 1, 2021. It is now read-only.
Folks have noted that "virtual" is not a good prefix for the current proposal, as it doesn't do traditional virtualization, and that prefix scares people off from using this as widely as we would like. We want something that doesn't connote "only use this in special circumstances", but instead "use this whenever you have some content of which not all is visible". In other words, we want something that encourages all of the use cases, including short scrollers.
And "scroller" isn't that great either, as our latest designs don't necessarily scroll unless they're placed into a container/viewport that is smaller than they are. We briefly started using <virtual-content> for this, but we realized it was confusing to have an element name that was different from the repository name, so now the explainer only talks about <virtual-scroller>.
But. Renaming is costly, mainly in how causes community confusion as everyone reorients themselves. So, we want to do it as rarely as possible. Let's wait for the design and implementation to progress further, and then consider a new, hopefully more final, name. In the meantime, this is just a tracking issue.
The text was updated successfully, but these errors were encountered:
I think scroller is fine, in the sense that it is expected that if everything is contained it won't scroll, but in that case it should show scroll effects like on Android and iOS. (Like end of scrollable region reached).
I think that I personally would like a name like 'scrollable' instead of 'scroller', or maybe scrollable container
Folks have noted that "virtual" is not a good prefix for the current proposal, as it doesn't do traditional virtualization, and that prefix scares people off from using this as widely as we would like. We want something that doesn't connote "only use this in special circumstances", but instead "use this whenever you have some content of which not all is visible". In other words, we want something that encourages all of the use cases, including short scrollers.
And "scroller" isn't that great either, as our latest designs don't necessarily scroll unless they're placed into a container/viewport that is smaller than they are. We briefly started using
<virtual-content>
for this, but we realized it was confusing to have an element name that was different from the repository name, so now the explainer only talks about<virtual-scroller>
.But. Renaming is costly, mainly in how causes community confusion as everyone reorients themselves. So, we want to do it as rarely as possible. Let's wait for the design and implementation to progress further, and then consider a new, hopefully more final, name. In the meantime, this is just a tracking issue.
The text was updated successfully, but these errors were encountered: