0 replies
🇳🇱johnny8d📡
Reply #2 — More content to push the scroll area. The scroll-lock toggle in the header should keep us pinned to the bottom.2 vars
🇳🇱johnny8d📡
Reply #3 — Filling the thread. Each reply should be visible at the bottom as it arrives via WebSocket.2 vars
🇳🇱johnny8d📡
Reply #4 — Getting closer to viewport overflow. If we have enough replies the parent post should scroll out of view.2 vars
🇳🇱johnny8d📡
Reply #5 — This should be well past the fold now. The newest reply must be visible at the bottom with scroll-lock ON.2 vars
🇳🇱johnny8d📡
Reply #6 — Adding more content. This is a longer reply to take up more vertical space in the thread view. We need enough content to push the scrollable area past the viewport boundary so we can properly test the scroll-lock auto-scroll behavior.1 var
🇳🇱johnny8d📡
Reply #7 — Continuing to fill. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris.1 var
🇳🇱johnny8d📡
Reply #8 — Still filling. The parent post at the top should now be scrolled out of view if scroll-lock is keeping us pinned to the bottom. This is the critical test — does the view stay at the bottom as new messages arrive?1 var
🇳🇱johnny8d📡
Reply #9 — Nearly there. At this point the thread should definitely overflow. If you can see this message, auto-scroll is working correctly. The scroll-lock toggle in the header should show the down-arrow icon in accent color.1 var