# Discourse composer and Firefox on Android tablet

**URL:** https://meta.discourse.org/t/discourse-composer-and-firefox-on-android-tablet/346876
**Category:** UX
**Tags:** tablet, fixed
**Created:** [January 13, 2025, 2:18pm UTC](https://meta.discourse.org/t/discourse-composer-and-firefox-on-android-tablet/346876 "2025-01-13T14:18:55Z")
**Posts on this page:** 1
**Showing post:** 14

<div class="post-metadata">

### Author: ![pmusaraj](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pmusaraj/32/119489_2.png) [@pmusaraj](https://meta.discourse.org/u/pmusaraj)
#### Post date: [January 14, 2025, 3:49pm UTC](https://meta.discourse.org/t/discourse-composer-and-firefox-on-android-tablet/346876/14 "2025-01-14T15:49:39Z")

</div>

> [@Moin](#):
>
> And it wasn’t a problem in Firefox a week ago.

Right, we made some changes to the composer positioning to fix some longstanding issues, see [Reply composer broken on firefox mobile - #6 by pmusaraj](https://meta.discourse.org/t/reply-composer-broken-on-firefox-mobile/341110/6)

> [@Moin](#):
>
> in Chrome it does not matter whether I activate “desktop-site” in it’s settings

Yeah, I am getting the same results from Chrome, toggling Desktop Site has no effect. When I inspect the user agent with or without that toggle, Chrome has some subtle differences, but crucially neither mode has `Mobile` in the user agent.

In Firefox, with Desktop Site disabled, I see:

 ![CleanShot 2025-01-14 at 10.49.11@2x](https://global.discourse-cdn.com/meta/original/4X/f/6/8/f6890d872436ea4d6587c0c0ec2abc3104606e9c.jpeg)

---

_[View the full topic](https://meta.discourse.org/t/discourse-composer-and-firefox-on-android-tablet/346876)._
