Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scroll jumps after switching rooms #121

Closed
quinthar opened this issue Aug 12, 2020 · 6 comments
Closed

Scroll jumps after switching rooms #121

quinthar opened this issue Aug 12, 2020 · 6 comments
Assignees

Comments

@quinthar
Copy link
Contributor

When switching from room A to B, it seems like we start out scrolled almost to the bottom, but not quite -- and then a half-second later, it switches to the bottom entirely.

Marking HIGH because it's very visible and contributes to a "flakey" sense that we really want to avoid as a first impression. It's totally fine to think "Ah, this isn't complete" -- but for the things that do work, they need to be fast and rock solid.

@quinthar quinthar added the HIGH label Aug 12, 2020
@quinthar quinthar added this to the Alpha Launch milestone Aug 12, 2020
@tgolen
Copy link
Contributor

tgolen commented Aug 12, 2020

I think @AndrewGable is fixing this so I will reassign.

@tgolen tgolen assigned AndrewGable and unassigned tgolen Aug 12, 2020
@AndrewGable
Copy link
Contributor

Looking into this today after we get iOS off the ground

@AndrewGable AndrewGable added CRITICAL and removed HIGH labels Aug 14, 2020
@AndrewGable
Copy link
Contributor

Briefly stated looking into this (branch). I was going to split native and web up here and use the old ScrollView for web and FlatList for native layers.

@quinthar
Copy link
Contributor Author

Briefly stated looking into this (branch). I was going to split native and web up here and use the old ScrollView for web and FlatList for native layers.

Hm, I really don't like that idea at all -- why is this necessary? That seems a concession to platform-specific code right out of the gate.

@AndrewGable
Copy link
Contributor

Actually I would love to know if you experience this issue still, I think it was improved quite a bit since the issue was created and am interested if it's still valid.

@quinthar
Copy link
Contributor Author

This seems either solved or dramatically improved, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants