# Dealing with iOS 8 Mobile Safari bugs?

**URL:** <https://meta.discourse.org/t/dealing-with-ios-8-mobile-safari-bugs/24101>\
**Category:** Feature\
**Created:** [1월 16, 2015, 8:28오후 UTC](https://meta.discourse.org/t/dealing-with-ios-8-mobile-safari-bugs/24101 "2015-01-16T20:28:13Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![iamntz](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/iamntz/32/114670_2.png) [@iamntz](https://meta.discourse.org/u/iamntz)\
**Post date:** [2월 12, 2015, 2:11오후 UTC](https://meta.discourse.org/t/dealing-with-ios-8-mobile-safari-bugs/24101/16 "2015-02-12T14:11:22Z")

</div>

Hi guys, I have an idea that could make the whole thing more usable on iOS. Since i have some troubles on getting a working dev version, i can explain how to fix it. And there are two kind of fixes:

The most easiest way to fix is to add when compose window is visible:

```plaintext
body, html {height:100%; overflow:hidden}

```

Surely, this will make impossible to scroll between existing posts, but.. at we will have a functional compose window.

The other solution would be a bit trickier to implement, but with good results. First, we need to move `#reply-control` div outside of `#main` div. Then, some CSS magic:

```plaintext
body, html {height:100%; overflow:hidden}
#main { height:100%; overflow:auto; -webkit-overflow-scrolling: touch; }
#reply-control { position:absolute }

```

In my quick tests (safari + GapDebug), everything play nicely.

---

_[View the full topic](https://meta.discourse.org/t/dealing-with-ios-8-mobile-safari-bugs/24101)._