# 在 Firefox (移动版) 中起草/编辑主题并不总是全屏

**URL:** https://meta.discourse.org/t/drafting-editing-a-topic-doesnt-always-go-fullscreen-in-firefox-mobile/239991
**Category:** Bug
**Created:** [2022年九月25日 07: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:** 1
**Showing post:** 2

<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: [2022年九月25日 08: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>

我认为这[之前已经报告过](https://meta.discourse.org/t/mobile-keyboard-hides-composer-using-microsoft-edge-on-android/228382/7?u=moin)，希望很快会有修复。

> <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

---

_[View the full topic](https://meta.discourse.org/t/drafting-editing-a-topic-doesnt-always-go-fullscreen-in-firefox-mobile/239991)._