Changes between Initial Version and Version 1 of Ticket #8307, comment 8


Ignore:
Timestamp:
Jul 27, 2015, 12:19:09 PM (9 years ago)
Author:
Szymon Cofalik
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #8307, comment 8

    initial v1  
    11After extensive week of trying to fix current maximize solution to fit iPad quirks I have to surrender, because hacking one bug lead to another one. Unfortunately, handling iframe that fills whole viewport and is scrollable is difficult. When keyboard is shown, it makes original viewport scrollable too, so we have a scrollable window in a scrollable window.
    22
    3 I tried to fit iframe's height to be viewport height - iOS keyboard height and partially managed to do so, but the viewport was still scrollable (it had "empty" <html> behind it and it was possible to still scroll down). AFAIR I managed to fix this behavior by preventing scroll event when editor reached certain scroll and when screen was touched at too low position. Then other problems occured: iframe's scroll started to jump all over the place when typing letters.
     3I tried to fit iframe's height to be `viewport height` minus `iOS keyboard height` and partially managed to do so. However, the viewport was still scrollable (it had "empty" <html> behind it and it was possible to still scroll down). AFAIR I managed to fix this behavior by preventing scroll event when editor reached certain scroll and when screen was touched at too low position. Then other problems occured: iframe's scroll started to jump all over the place when typing letters.
    44
    55I haven't found a good solution for the last problem that didn't introduce heavy UX flaws and at that point the code was really messy and hacked so I come to conclusion that it is not worthy to go even deeper this way.
© 2003 – 2022, CKSource sp. z o.o. sp.k. All rights reserved. | Terms of use | Privacy policy