"reply" experience on mobile

SomeoneElse · September 25, 2022, 10:59am

Can anything be done to improve the website-replying on mobile experience? Right now, on a phone that’s not that old**, it’s dreadful.

There’s a noticeable delay as all the javascript floating windows whizz around. The reply box is placed and sized incorrectly for the screen dimensions so that when the on-screen keyboard appears the bit of the reply box that I actually want to type in isn’t visible.

There’s always the option to turn on emails for everything and reply there, but not everyone will want to do that.

PS: and even on a desktop*** the “reply / create topic / send” button is hidden behind something that wants to tell me the URL of the page that I’m on, and because it’s not a proper window (it’s only Javascript pretending to be one) I can’t move it.

** 4-year-old Nokia 6.1, Android 9, Font size large, display size large, latest Firefox.

*** KDE, Ubuntu 18.04, latest Firefox.

nukeador · September 25, 2022, 11:04am

It seems there is a bug with some browsers on mobile, I also have to simulate a scroll up to get the compose box to go full screen.

Is anyone using the Discourse app also affected?

mmd · September 25, 2022, 11:16am

I’m typing this on iOS using Chrome (or Safari) as browser. Experience is pretty good, no complaints from my side.

When I start typing, the page automatically resizes to leave enough space for the on screen keyboard.

nukeador · September 25, 2022, 11:34am

It feels the chrome culture hits again and devs need to optimize for the default browser even if it’s a broswer bug and a hack affects other browsers

(that’s my understanding of the upstream conversation)

Discostu36 · September 25, 2022, 2:51pm

I have the problem of the hidden answer box on Firefox mobile in Discourse forums for months now, if not years. I am not holding my breath that this will be fixed soon.

nukeador · September 25, 2022, 5:33pm

We can bump the original upstream topic looking for workarounds.

nukeador · September 25, 2022, 8:11pm

Fix is in progress and might get included in the next version

github.com/discourse/discourse

FIX: Better virtual keyboard detect on Android

discourse:main ← discourse:android-keyboard-fixes-3

opened 07:35PM - 20 Sep 22 UTC

xfalcox

+54 -12

Firefox has a bug where *sometimes* the visualViewport.height won't be updated w…hen the keyboard pops up until you scroll, making our composer stay hidden behind the keyboard. This commit uses both window.innerHeight and window.visualViewport.height using the minimum of both to check for height changes. For Chrome/Edge we feature detect the new VirtualKeyboard API and opt-into it when the composer opens and use it to detect if a keyboard is being draw. Opting into the API changes how the viewport is calculated so we have to also change how the full height composer is calculated. To minimize breakage we opt-out when the composer component is destroyed. This commit also moves the `--composer-ipad-padding` to only happen on iPads. Bug report at https://meta.discourse.org/t/-/228382

SLMapper · December 23, 2022, 9:57am

Any update or work around for this? I also have the same issue in Firefox and I have not found a reliable way to overcome it.

Discostu36 · December 23, 2022, 12:05pm

I think we have to wait until Discourse 2.9 is released .

SLMapper · December 23, 2022, 12:54pm

Thanks. Is there any work around like e.g. dragging the window at a specific position or doing xy first?

RobJN · December 23, 2022, 1:18pm

Hmm, odd. I use Firefox on mobile and haven’t noticed an issue. I’m using “uBlock Origin” plugin too. edit: seems like uBlock is switched off on the forum.