We had so many issues like this at Medium, too.
-
-
I wouldn't be so quick to blame Twitter. Many bugs wrt spacing and c&p ended up being browser bugs when we dug in (cf https://bugs.chromium.org/p/chromium/issues/detail?id=318925 …)
1 reply 0 retweets 2 likes -
HTML spacing rules are complex. Any editing surface that treats the HTML as the "data model" is vulnerable to this issue. It's a problem for both native and JS impls.
1 reply 0 retweets 3 likes -
Replying to @nicksantos @mwichary
IMO this isn't a valid excuse for a bad user experience even if it's a valid reason. From the user's standpoint, the app owns the entire experience. Every company I've worked for has deployed numerous workarounds for hardware bugs instead of saying "yolo, it's hardware's fault".
1 reply 0 retweets 4 likes -
It's not uncommon for cloud vendors to get hardware firmware in order to fix bugs, but twitter can't fix bugs in open source browsers? It might be the right business decision to ship an app where text input is broken but, IMO, that doesn't somehow make it the browser's fault.
2 replies 0 retweets 3 likes -
I agree! Not an excuse, just providing historical/technical context for the curious!
1 reply 0 retweets 0 likes -
IMO the bugs are rooted in fundamental design flaws in the browser editing component. There was a proposal to redesign the APIs, but the w3c discussion ran into an impasse that is too complicated to fit in this tweet.
1 reply 0 retweets 0 likes -
Replying to @nicksantos @danluu
Argh, I was curious about whether some new API was coming. It’s disenchanting to see text being so maligned and hard to deal with, particularly as we learned many of the design lessons decades ago. :·/
1 reply 0 retweets 2 likes -
I switched to the new Firefox full-time out of curiosity, and I’m seeing problems that I haven’t on Chrome. Shouldn’t be the case.
1 reply 0 retweets 1 like -
Replying to @mwichary @nicksantos
Same here, although FWIW this particular bug predates the new FF and I saw it before upgrading. I think it was introduced/exposed by the change to 280 chars, which seems to have introduced/exposed *a lot* of issues.
1 reply 0 retweets 1 like
Wow. Unrelated (maybe?) to Twitter, but I just had Firefox fail multiple times at copy/pasting plain text. That’s… not something that should ever break. Even virtual machines/emulators do that well these days.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.