Conversation

Notices

1. Embed this notice
   mhoye (mhoye@mastodon.social)'s status on Monday, 11-Sep-2023 09:19:05 JST mhoye

   Write a long reply to a long, involved post.

   Pull down the screen a bit so you can re-read the post you’re replying to.

   Pull down a hair too far. Trigger a reload.

   Lose the reply I wrote.

   I want to keep using Mastodon in a browser but this is _killing me_. Ok, off to file a bug.

   • Embed this notice
     Eugen Rochko (gargron@mastodon.social)'s status on Monday, 11-Sep-2023 09:18:59 JST Eugen Rochko

     in reply to

     • かき@GNUsocialJP
     • SpaceLifeForm

     @mhoye @SpaceLifeForm This is browser behaviour. I'm not even sure websites have any way of overriding it.

   • Embed this notice
     mhoye (mhoye@mastodon.social)'s status on Monday, 11-Sep-2023 09:19:00 JST mhoye

     in reply to

     • SpaceLifeForm

     @SpaceLifeForm yeah, it sort of looks like this:

   • Embed this notice
     mhoye (mhoye@mastodon.social)'s status on Monday, 11-Sep-2023 09:19:00 JST mhoye

     in reply to

     • SpaceLifeForm

     @SpaceLifeForm the whole pull-down-to-refresh thing is great everywhere except when I’m replying to a post, and then it is doom.

   • Embed this notice
     mhoye (mhoye@mastodon.social)'s status on Monday, 11-Sep-2023 09:19:03 JST mhoye

     in reply to

     • SpaceLifeForm

     @SpaceLifeForm mobile, iOS

   • Embed this notice
     SpaceLifeForm (spacelifeform@infosec.exchange)'s status on Monday, 11-Sep-2023 09:19:03 JST SpaceLifeForm

     in reply to

     @mhoye

     Thanks. IOS seems to be a factor.

   • Embed this notice
     SpaceLifeForm (spacelifeform@infosec.exchange)'s status on Monday, 11-Sep-2023 09:19:05 JST SpaceLifeForm

     in reply to

     @mhoye

     Desktop or mobile? #Debugging

   • Embed this notice
     mhoye (mhoye@mastodon.social)'s status on Monday, 11-Sep-2023 09:38:01 JST mhoye

     in reply to

     • Eugen Rochko
     • SpaceLifeForm

     @Gargron @SpaceLifeForm

     I’m 100% ready to believe you, if you say this is a unsolvable Apple/WebKit problem.