# WebDirect in FMS20 on iPad

**URL:** <https://the.fmsoup.org/t/webdirect-in-fms20-on-ipad/3910>\
**Category:** Questions\
**Tags:** webdirect, ipad\
**Created:** [January 14, 2024, 4:01pm UTC](https://the.fmsoup.org/t/webdirect-in-fms20-on-ipad/3910 "2024-01-14T16:01:14Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![xochi](https://avatars.discourse-cdn.com/v4/letter/x/0ea827/32.png) [@xochi](https://the.fmsoup.org/u/xochi)\
**Post date:** [January 14, 2024, 4:01pm UTC](https://the.fmsoup.org/t/webdirect-in-fms20-on-ipad/3910/1 "2024-01-14T16:01:14Z")

</div>

This is a followup to [WebDirect 18 bugs: fixed in 19?](https://the.fmsoup.org/t/webdirect-18-bugs-fixed-in-19/1488)

One bug that seems to still exist in FMS 20 WebDirect:

- on an iPad in Safari
- if your WebDirect layout is taller than the screen
- scrolling is buggy

The "solution" as described [here](https://community.claris.com/en/s/feed/0D50H00007F6IbjSAF) is to use Safari to "Request Mobile Website" at which point the page works much better.

This was not a great solution in 2019, and 4+ years later it's pretty amazing this bug still exists.

Anyone found a way to deal with this? I'm thinking...

- different layouts for different screen sizes
- some sort of javascript hack in the WebDirect files to fix or work around the bug

---

<div class="post-metadata">

**Author:** ![FileKraft](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/filekraft/32/1183_2.png) [@FileKraft](https://the.fmsoup.org/u/FileKraft)\
**Post date:** [January 14, 2024, 4:11pm UTC](https://the.fmsoup.org/t/webdirect-in-fms20-on-ipad/3910/2 "2024-01-14T16:11:36Z")

</div>

Please always report your bugs to Clairs - thanks for sharing @xochi.

---

<div class="post-metadata">

**Author:** ![xochi](https://avatars.discourse-cdn.com/v4/letter/x/0ea827/32.png) [@xochi](https://the.fmsoup.org/u/xochi)\
**Post date:** [January 14, 2024, 4:15pm UTC](https://the.fmsoup.org/t/webdirect-in-fms20-on-ipad/3910/3 "2024-01-14T16:15:03Z")

</div>

> [@FileKraft](#):
>
> Please always report your bugs to Clairs

Yes, the link I provided is to a bug report submitted in 2019, so clearly Claris is (was?) aware of the issue. It may be worth re-reporting to remind them? 🙂

---

<div class="post-metadata">

**Author:** ![FileKraft](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/filekraft/32/1183_2.png) [@FileKraft](https://the.fmsoup.org/u/FileKraft)\
**Post date:** [January 14, 2024, 4:34pm UTC](https://the.fmsoup.org/t/webdirect-in-fms20-on-ipad/3910/4 "2024-01-14T16:34:23Z")

</div>

If you reported it then (2019), report it again for the current version if applicable. Sadly you have to report over and over again as far as I experienced it just to increase the likelihood to get notices first and if ever fixed ...

---

<div class="post-metadata">

**Author:** ![Malcolm](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/malcolm/32/196_2.png) [@Malcolm](https://the.fmsoup.org/u/Malcolm)\
**Post date:** [January 15, 2024, 7:30am UTC](https://the.fmsoup.org/t/webdirect-in-fms20-on-ipad/3910/5 "2024-01-15T07:30:56Z")

</div>

My solution is to standardise layouts around the minimum screen size and then stretch-to-fit.

It doesn't always work. Some layouts have too much info and its much easier for the user to scroll up/down than it is to split the data across tabs, panels, or layouts.