perf: implement IntersectionObserver lazy loading wrapper for chat attachments (#347)#529
Conversation
|
Warning Review limit reached
More reviews will be available in 50 minutes and 27 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
@UTKARSHH20 please check it and merge it |
Closes #347
Changes Made:
frontend/src/components/chat/LazyMedia.jsx) leveraging the native WebIntersectionObserverAPI.<img>and<audio>attachment elements. Assets remain un-rendered as structural lightweight skeleton placeholders until the specific message frame approaches the active scrolling window layout parameters.200pxroot margin offset barrier to dynamically fetch assets immediately prior to visual boundary impact, maintaining a seamless, zero-lag rendering UX.