# Composer positioning issues in iOS
**URL:** https://meta.discourse.org/t/composer-positioning-issues-in-ios/388476
**Category:** Bug
**Tags:** ios
**Created:** [November 9, 2025, 9:03pm UTC](https://meta.discourse.org/t/composer-positioning-issues-in-ios/388476 "2025-11-09T21:03:14Z")
**Posts on this page:** 20
**Page:** 1
### Author:  [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [November 9, 2025, 9:03pm UTC](https://meta.discourse.org/t/composer-positioning-issues-in-ios/388476/1 "2025-11-09T21:03:14Z")
Just want to let you all know we are working on a fix to improve the composer on iOS. Hopefully something should come out this week.
---
### Author:  [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [November 13, 2025, 11:11pm UTC](https://meta.discourse.org/t/composer-positioning-issues-in-ios/388476/2 "2025-11-13T23:11:22Z")
Sorry it’s taking so much time, I have been working a lot on this lately and trying various solutions internally, none is perfect so far, but Im getting close.
---
### Author:  [@Ethsim2](https://meta.discourse.org/u/Ethsim2)
#### Post date: [November 16, 2025, 10:07am UTC](https://meta.discourse.org/t/composer-positioning-issues-in-ios/388476/4 "2025-11-16T10:07:07Z")
meta and my up-to-date instance both have same problem with “Save Edit” not responding if the keyboard isn’t collapsed, or needing the type cursor vertical line to be sometimes 1, sometimes many lower than where’s being edited.
---
### Author:  [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [November 18, 2025, 11:36pm UTC](https://meta.discourse.org/t/composer-positioning-issues-in-ios/388476/5 "2025-11-18T23:36:57Z")
Im deploying meta with a version containing fixes related to iOS (not only the composer). Let me know how it goes for you, should be deployed one hour from 2025-11-18T23:36:00Z
> [@Ethsim2](#):
>
> meta and my up-to-date instance both have same problem with “Save Edit” not responding if the keyboard isn’t collapsed, or needing the type cursor vertical line to be sometimes 1, sometimes many lower than where’s being edited.
Im not sure this is going to fix this, but it’s possible let me know if you still have it. And if you still have it, do you have it as often as before?
---
### Author:  [@seanblue](https://meta.discourse.org/u/seanblue)
#### Post date: [November 19, 2025, 5:43am UTC](https://meta.discourse.org/t/composer-positioning-issues-in-ios/388476/6 "2025-11-19T05:43:15Z")
It seems to work as far as I can tell.
There’s another fairly recent issue where closing the keyboard makes the composer full screen. Previously, doing so would move the composer to the bottom half of the screen (roughly where the keyboard was), allowing me to view the post I’m replying to. Now I have to manually minimize the composer with the double down arrow button. Is this related to these recent iOS issues or should I submit a separate bug report?
---
### Author:  [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [November 19, 2025, 6:10am UTC](https://meta.discourse.org/t/composer-positioning-issues-in-ios/388476/7 "2025-11-19T06:10:26Z")
> [@seanblue](#):
>
> Is this related to these recent iOS issues, or should I submit a separate bug report?
It’s a #design-experiment
> [@Mobile composer: permanent full-screen (update: in core)](https://meta.discourse.org/t/mobile-composer-permanent-full-screen/374766):
>
> Summary Mini experiment to keep mobile composer full-height, even when closing the keyboard. Reason Avoid jumpy movements when interacting within composer, whenever the keyboard closes or opens Make re-reading your own post before submitting easier by using the fully available sceen Screenshots Before After Notes To see the forum while composing, you can still use the dedicated minimise button in the top right corner. There may be potential differences in ex…
---
### Author:  [@Ethsim2](https://meta.discourse.org/u/Ethsim2)
#### Post date: [November 19, 2025, 8:28am UTC](https://meta.discourse.org/t/composer-positioning-issues-in-ios/388476/8 "2025-11-19T08:28:27Z")
> [@j.jaffeux](#):
>
> And if you still have it, do you have it as often as before?
i still have it, though i can’t comment on how often yet
---
### Author:  [@Wingtip](https://meta.discourse.org/u/Wingtip)
#### Post date: [November 19, 2025, 6:30pm UTC](https://meta.discourse.org/t/composer-positioning-issues-in-ios/388476/9 "2025-11-19T18:30:48Z")
Looking forward to this going live. Discourse has been nearly unusable on iOS for many months now. And now typing this post on my iPad it’s perfectly fine— even though the compose panel is not maximized. So whatever you did, it worked.
---
### Author:  [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [November 20, 2025, 11:19am UTC](https://meta.discourse.org/t/composer-positioning-issues-in-ios/388476/10 "2025-11-20T11:19:42Z")
Hopefully we merge this week 🤞 but thanks for letting me know it improves things for you.
---
### Author:  [@mentalstring](https://meta.discourse.org/u/mentalstring)
#### Post date: [November 20, 2025, 2:31pm UTC](https://meta.discourse.org/t/composer-positioning-issues-in-ios/388476/11 "2025-11-20T14:31:30Z")
I usually don’t interact with Discourse via iOS, but gave it a go and for the most part, it is working as expected. 👍 To me this feels usable although, admittedly, I’m probably not familiar with all the ways it is/was not working correctly.
The only issue I found was the one already reported [here](https://meta.discourse.org/t/ios-26-bugs-still-persist-on-26-1/387922/1) which happens when switching to another app and when returning to Discourse — then the cursor is one line below where one is actually typing. Once that happens, it’s a little finicky to get back to normal state.
---
### Author:  [@Ethsim2](https://meta.discourse.org/u/Ethsim2)
#### Post date: [November 20, 2025, 3:39pm UTC](https://meta.discourse.org/t/composer-positioning-issues-in-ios/388476/12 "2025-11-20T15:39:49Z")
it’s continuing to happen, after rebuild this morning
---
### Author:  [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [November 20, 2025, 4:56pm UTC](https://meta.discourse.org/t/composer-positioning-issues-in-ios/388476/13 "2025-11-20T16:56:41Z")
We have merged nothing yet, so a rebuild is expected to not fix anything.
---
### Author:  [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [November 20, 2025, 4:58pm UTC](https://meta.discourse.org/t/composer-positioning-issues-in-ios/388476/14 "2025-11-20T16:58:32Z")
On my current tests on meta, this almost never happens anymore wether though the collapsing repro mentioned in the link post, or your note of switching from one app to another. I know it can still happen from time to time, especially on PWA, but I can only fix some of the bugs of apple 🤷♂️ and PWA is clearly the worst of all, direct browsing in safari or discourse app is less buggy AFAIK.
Note that I have plans, to fully revamp how the composer is displayed on mobile, but this is longer term plan, those fixes are mostly trying to extinguish the fires created by Apple, I also hope in the next weeks they will keep fixing more bugs.
---
### Author:  [@mentalstring](https://meta.discourse.org/u/mentalstring)
#### Post date: [November 20, 2025, 5:18pm UTC](https://meta.discourse.org/t/composer-positioning-issues-in-ios/388476/15 "2025-11-20T17:18:37Z")
> [@j.jaffeux](#):
>
> discourse app is less buggy AFAIK.
FWIW, I only tested it using the Discourse app, and I can consistently reproduce the issue of switching to another app and returning. Sometimes the cursor looks to be in the right place, but when typing it’s actually not ok.
Anyhow, not saying this is a big issue, just reporting my experience. Let me know if I can be of help with more info.
---
### Author:  [@Wingtip](https://meta.discourse.org/u/Wingtip)
#### Post date: [November 20, 2025, 8:57pm UTC](https://meta.discourse.org/t/composer-positioning-issues-in-ios/388476/16 "2025-11-20T20:57:32Z")
Meta still seems fine to me, no issues with the cursor being off a couple of lines from the typing spot and the reply button touch target is where it appears on screen, not an inch below.
---
### Author:  [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen)
#### Post date: [November 20, 2025, 9:38pm UTC](https://meta.discourse.org/t/composer-positioning-issues-in-ios/388476/17 "2025-11-20T21:38:20Z")
I had some strangeness today when looking for a gif to insert in chat. Seems to work fine when posting in the forum.
---
### Author:  [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [November 21, 2025, 1:54pm UTC](https://meta.discourse.org/t/composer-positioning-issues-in-ios/388476/18 "2025-11-21T13:54:14Z")
Yes I saw this one, I will fix it once the PR is merged (which I just did 🚀), it needs a fix in discourse-gifs
---
### Author:  [@Wingtip](https://meta.discourse.org/u/Wingtip)
#### Post date: [November 21, 2025, 6:21pm UTC](https://meta.discourse.org/t/composer-positioning-issues-in-ios/388476/19 "2025-11-21T18:21:35Z")
This fixed it! Thanks, this bug was like, _supernaturally_ annoying. It made me actively avoid using Discourse on iOS.
---
### Author:  [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [November 23, 2025, 9:10am UTC](https://meta.discourse.org/t/composer-positioning-issues-in-ios/388476/20 "2025-11-23T09:10:52Z")
Sadly it can still happen in rare cases, it’s not something I consider fully solved, but yes it should be a LOT better. Fixing it to 100% will take me much more time.
---
### Author:  [@Shauny](https://meta.discourse.org/u/Shauny)
#### Post date: [November 23, 2025, 9:11am UTC](https://meta.discourse.org/t/composer-positioning-issues-in-ios/388476/21 "2025-11-23T09:11:26Z")
When is this fix available to self-hosted sites?
[Next page](https://meta.discourse.org/t/composer-positioning-issues-in-ios/388476.md?page=2)