Fix Basic Mobile Chrome & Safari Navigation

Feedback
1

For the last 6 month the majority of my users have been unable to use my stacker built solutions in their most readily available web browsers. Stacker users of the top naviagtion configuration are completely unable to access the navigation bar because of some sort of “fit anomaly” in Chrome and Safari Mobile.

When i brought this to the stacker admin teams attention months ago i was told that we should use some other browser, such as firefox, this is an insufficient solution.

2

Hi @Nick

Please can you send a message to support, that way we can track the issue you opened.

Thank you!

3

Sure thing thu, its just been quite a while with no resolution and my team is under pressure. Ill try there again

4

Heya, Nick! Indeed, I’m sorry for the trouble. That bug is a huge pain, for me as well. But as it isn’t our bug, it isn’t something we can fix for you. :frowning:

The browser should not cover the webpage with its UI, but we can’t stop them if they do. This happens only in Chrome and Safari on iPadOS, and will likely require an update at the OS level (Chrome uses Safari’s webview, though the fact that this doesn’t happen in others suggests they may be using the APIs differently). And while we have tried to find some workaround, we have not been able to (and, frankly, doing so could just cause more problems if it’s fixed in the OS, or in others which are fine). But, as I mentioned previously, any of the following will work:

  • Using side navigation in the Stacker app instead, since it is only the top navigation that the browser UI is hiding

  • Multitasking away from Safari and then back to it – it stops hiding the top navigation after that for some reason

  • Using another browser which does not suffer from this bug, e.g. Firefox, Brave, DuckDuckGo, etc. – I haven’t been able to find any other than Chrome and Safari where this happens

I appreciate that this isn’t ideal, and I’d be annoyed too, but it’s not something we have control over here at Stacker, and using one of the above workarounds (side navigation would be easiest for your users) will help. Thanks for understanding. :pray: