Skip to content
This repository has been archived by the owner on Dec 1, 2021. It is now read-only.

Fixed transactions page scrolling issue #511

Draft
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

MonikaCat
Copy link
Contributor

Description

Fixes #447

Checklist

  • Targeted PR against correct branch.
  • Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
  • Run meteor npm run lint
  • Added an entry to the CHANGELOG.md file.
  • Re-reviewed Files changed in the Github PR explorer.

@MonikaCat MonikaCat requested a review from kwunyeung May 6, 2021 08:20
@@ -9,7 +9,7 @@ export default ValidatorDetailsContainer = withTracker((props) => {

if (Meteor.isClient){
transactionsHandle = Meteor.subscribe('transactions.list', props.limit);
loading = !transactionsHandle.ready();
loading = !transactionsHandle.ready() && props.limit == Meteor.settings.public.initialPageSize;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MonikaCat yes this would fix the display issue. However, if the txs are being loaded continuously, the DOM will be rendering too many components if the users keeps scrolling. Can you do a test and see if the screen will be laggy after some scrolls?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure! The screen becomes a little bit laggy after scrolling down multiple times.

I have wrapped the list in Container so we can track scrolling only of the list component. The overall performance of the page has improved and the transactions are loading faster. What do you think?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't understand. Why wrapped inside a <Container> would improve performance? I think the <List> component is still querying and rendering components controlled by limit?

@MonikaCat MonikaCat marked this pull request as draft May 27, 2021 09:31
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Scrolling to the bottom of the transaction page reloads the page and goes to the top
2 participants