[Bug] Another regression, glitchy liquidity pool page
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.5k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
📱 Interface Affected
Which application are you experiencing issues with?
- Web (app.uniswap.org)
- Wallet Extension (wallet.uniswap.org)
- Wallet Mobile App
- iOS
- Android
- Both
🧩 App Version
- Version (if known):
- Production build
- Development build
💻 System / Environment Info
Please provide details about your environment:
- Browser (name + version): Chrome
- OS / Platform (e.g. iOS 17, Windows 11, Android 14):
- Device (e.g. iPhone 14 Pro, Pixel 7, MacBook Pro 2023):
- Wallet used (e.g. Uniswap Wallet, MetaMask, Rainbow): Metamask
- Network (e.g. Ethereum Mainnet, Arbitrum, Base, etc.):
🔁 Steps to Reproduce
- Go to the Pools page.
- Have a few liqudity pools, some open-inrange, some closed.
✅ Expected Behavior
- All my pools show up right away (how it was before)
- The page does not keep glitching (see video)
❌ Actual Behavior
- Takes a while for my pools to load (much longer than before)
- Only loads some, then takes a while to show more
- Glitches on the screen
📸 Screenshots or Screen Recording
https://github.com/user-attachments/assets/704e7c1e-d519-46ca-8284-88b313e70037
🧾 Additional Context
The app is getting worse for me as an LP as you all do more development. Please, check our organization's QA process and consider making some changes.
⚠️ Please redact or avoid sharing sensitive data such as private keys, seed phrases, or personally identifying info.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the problem from the Pools page at app.uniswap.org in Chrome with MetaMask, using pools that are both in-range and closed. Compare the delayed loading, partial results, and screen glitches with the expected behavior that all pools appear promptly without visual glitches; the issue names no source file or test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100