zlacker

>>ZacnyL+(OP)
I don't see any unusual behavior when looking at the debugger in Chrome. People have a political issue with Elon. Which is fine. People are entitled to it.

>>TheBli+qO
The post suggests a race condition as the underlying cause of the behavior shown in screen captures. It’s perfectly possible the race condition does exist, and being a race condition you just didn’t happen to trigger it. It’s also perfectly possible to discover such a defect with or without any personal bias towards Musk or Twitter.

Reporting it publicly this way can also be a favor to both, as it gives them a fairly malleable narrative for reversing course, or directing responsibility, or both. Even if it’s simultaneously embarrassing to have it out there. And it’s not like either Musk or Twitter is a stranger to embarrassment, or particularly shy about courting it.

>>eyelid+FP
Clearly there is something wrong with the site. So I don't doubt there is a bug. But the OP gives no helpful information that could be used to reproduce the issue and fails to describe it in any helpful detail really. They seem content to just effectively say "Twitter is dumb." Which, again, is fine but not all that technical and interesting.

>>TheBli+ZP
There’s information in the post that very probably points at the underlying cause. The scrollbar jumping is a dead giveaway: Twitter loads more content based on scroll position. If your viewport is sized such that displaying the error message triggers another load event by its corresponding change in scroll position, it will try again indefinitely absent some additional logic to bail out.

Edit: this of course depends on some other implementation details, like the rendering flow and browser behavior. If showing the error is memoized, it shouldn’t trigger the loop unless they’re also rendering some intermediate loading state asynchronously.