pull down to refresh

222 sats \ 9 replies \ @optimism 11h \ parent \ on: Stacker Saloon

Saw some odd editor behavior on android PWA, will try to repro and file you an issue later today or tomorrow.

write
preview
100 sats \ 4 replies \ @k00b 10h

Could be because what was a textarea before is now contenteditable=true. I'll check for weirdness on my devices.

reply
100 sats \ 3 replies \ @optimism 10h

Makes sense because it went away after reboot - caching issue?

reply
100 sats \ 2 replies \ @k00b 10h

I wouldn't be surprised but you have the new UI in your video which shouldn't contain stale references unless there's some bug upstream in our bundler or downstream in the browser cache.

I'll continue to be skeptical of contenteditable=true just to be safe.

reply
100 sats \ 1 reply \ @optimism 4h

It came back. I'll try to figure out what triggers it in the am.

reply
0 sats \ 0 replies \ @k00b 4h

Based on what sox was saying, it sounds like the browser wants to delete whole words and we are doing something that prevents that. We also deployed some fixes an hour ago, so it could still be some cache thing.

reply
100 sats \ 3 replies \ @sox 11h

That would be amazing, thank you.

reply
200 sats \ 2 replies \ @optimism 10h

It went away after a phone reboot, so may just be a caching issue... will build a full github issue if it comes back. Here's the screencap:

reply
100 sats \ 1 reply \ @sox 10h

This was actually really helpful, it’s something I can reproduce myself on iOS (although not like this).

iOS tries to delete whole words when holding the backspace button, this doesn’t work very well outside of a textarea. Will see how to make it consistent.

reply
100 sats \ 0 replies \ @optimism 10h

More evidence that iOS UX > Android UX <saddest face emoji>

Glad I realized I should boot between to exclude any secret system browser caches. Caching issues cross-upgrade are always forgivable.

reply