# La rédaction/modification d'un sujet ne passe pas toujours en plein écran dans Firefox (mobile)

**URL:** https://meta.discourse.org/t/drafting-editing-a-topic-doesnt-always-go-fullscreen-in-firefox-mobile/239991
**Category:** Bug
**Created:** [Septembre 25, 2022, 7:54 UTC](https://meta.discourse.org/t/drafting-editing-a-topic-doesnt-always-go-fullscreen-in-firefox-mobile/239991 "2022-09-25T07:54:11Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![AquaL1te](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/aqual1te/32/201966_2.png) [@AquaL1te](https://meta.discourse.org/u/AquaL1te)
#### Post date: [Septembre 25, 2022, 7:54 UTC](https://meta.discourse.org/t/drafting-editing-a-topic-doesnt-always-go-fullscreen-in-firefox-mobile/239991/1 "2022-09-25T07:54:12Z")

</div>

J’utilise la dernière version de Firefox sur Android 11 (Fairphone 4), je remarque que je me bats souvent avec l’interface utilisateur. Est-ce un comportement normal ? Je n’ai pas de navigateur Chrome (basé) sur mon téléphone, mais j’en ai vu d’autres l’utiliser. Là, c’était toujours fluide. Dois-je m’attendre à ce que Firefox soit moins testé et perfectionné lors de l’utilisation de Discourse ?

> **[New video · Thursday, Sep 22, 2022 🎬](https://photos.google.com/share/AF1QipOw8bc8pLnBeyx1wXGo16AD0R2LfZHH2tXwCCJf6pNPtRPWfax2ZUcbkipYFB31qg?key=TWl6X2diQVh1OUZNem80ZkNveVdjNEdneFJ6dDlB)**

---

<div class="post-metadata">

### Author: ![Moin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/moin/32/554653_2.png) [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [Septembre 25, 2022, 8:17 UTC](https://meta.discourse.org/t/drafting-editing-a-topic-doesnt-always-go-fullscreen-in-firefox-mobile/239991/2 "2022-09-25T08:17:50Z")

</div>

Je pense que cela a [été signalé auparavant](https://meta.discourse.org/t/mobile-keyboard-hides-composer-using-microsoft-edge-on-android/228382/7?u=moin) et qu’il y aura bientôt un correctif, espérons-le.

> <https://github.com/discourse/discourse/pull/18298>
>
> 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

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [Septembre 25, 2022, 7:56 UTC](https://meta.discourse.org/t/drafting-editing-a-topic-doesnt-always-go-fullscreen-in-firefox-mobile/239991/3 "2022-09-25T19:56:48Z")

</div>

Doublon de [Mobile keyboard hides composer using Microsoft Edge on Android](https://meta.discourse.org/t/mobile-keyboard-hides-composer-using-microsoft-edge-on-android/228382?u=falco)

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [Septembre 25, 2022, 7:56 UTC](https://meta.discourse.org/t/drafting-editing-a-topic-doesnt-always-go-fullscreen-in-firefox-mobile/239991/4 "2022-09-25T19:56:51Z")

</div>


