I’m using the latest Firefox on Android 11 (Fairphone 4), I notice that I’m often fighting the UI. Is this normal behavior? I don’t have a Chrome (based) browser on my phone, but I’ve others use it. There it was always smooth. Should I expect Firefox to be less tested and perfected when using Discourse?
Moin
2022 年9 月 25 日 08:17
2
I think this was reported before and hopefully there will be a fix soon.
discourse:main ← discourse:android-keyboard-fixes-3
opened 07:35PM - 20 Sep 22 UTC
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
4 个赞
Falco
2022 年9 月 25 日 19:56
3
2 个赞