Skip to content

Conversation

@federiconardelli7
Copy link
Collaborator

Fix the text while loading the C-chain page and L1 chains

image image

@federiconardelli7 federiconardelli7 requested a review from a team as a code owner November 17, 2025 21:45
@vercel
Copy link

vercel bot commented Nov 17, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
builder-hub Ready Ready Preview Comment Nov 19, 2025 6:46pm

@meaghanfitzgerald
Copy link
Collaborator

this is the loading screen im seeing
image

@meaghanfitzgerald
Copy link
Collaborator

c-chain page loading still looks odd, has a bullet point in front of the title and has a different aspect ratio than the loaded state it seems

@federiconardelli7
Copy link
Collaborator Author

image

Now it should be fixed for the C-chain and L1 pages.

Pushing when it goes up again.

@navillanueva
Copy link
Contributor

@federiconardelli7 can this be turned into a component/wrapper that we apply to all three loading stats? code looks repeated for the c-chain and the l1 page

@federiconardelli7
Copy link
Collaborator Author

@federiconardelli7 can this be turned into a component/wrapper that we apply to all three loading stats? code looks repeated for the c-chain and the l1 page

Yes and no, because it's the actual skeleton of what the page loaded looks like. So the overview page is different from the validator page and the chain page.
The C-chain and l1 page is the same (ChainMetricsPage.tsx), it automatically adjusts if there is or there is not the logo, displays the fixed texts, and blurs where the text needs to be displayed

@martineckardt martineckardt merged commit 3ba696a into master Nov 19, 2025
2 checks passed
@martineckardt martineckardt deleted the federiconardelli7/fix-loading-stats-screen-c-chain branch November 19, 2025 19:27
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

Successfully merging this pull request may close these issues.

5 participants