Uhg, Twitter just broke old-twitter (UA=IE11) by making it so clicking on tweets no longer pops them up, but loads a new page and loses your place. Presumably to frustrate us enough to get us to switch away?
Conversation
Replying to
I think that's a lot cause. I just wish the new tweet compose interface wasn't so buggy especially when using backspace. I keep making it crash and lose what I was writing. I did it while responding to you here. Can't even remember what I was in the process of writing before.
1
Replying to
I think I need to fake UA as a mobile browser because the mobile web version is the only one that doesn't suck.
1
Replying to
I used to like using that on the desktop because it's way lower latency / less bloated but apparently it's not simply available via mobile.twitter.com anymore or they replaced it with the new interface. I don't know...
1
The new interface is reinventing text input and text display instead of doing things via standard semantic HTML which is major part of why it's so messed up. I can't even select a whole paragraph with double click reliably and the tweet composition is ridiculously buggy.
Try double clicking on my tweet with a link. The link ends up screwing it up now. I don't know how they manage to break basic functionality like this or using backspace without crashing the entire web page somehow.
1
1
So, I looked at the HTML for my tweet since I was genuinely curious how they broke this and I'm horrified. How can I unsee this? Also, this is exactly what I'm talking about when I refer to web pages becoming insanely obfuscated messes where content filtering becomes impractical.
2
2
3
Show replies
Replying to
That's what I found when I used the preview. It seems to be using the same shit framework Patreon is with 2-3 sec input latency for each keystroke.