# 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:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![j.jaffeux](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/j.jaffeux/32/60297_2.png) [@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")

</div>

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?

---

_[View the full topic](https://meta.discourse.org/t/composer-positioning-issues-in-ios/388476)._