St.chat_input is either hidden or covered by the "hosted by streamit" icon on iphone

☁️ Community Cloud
1

Two, realted issues.

  1. The placement of the Hosted by Streamlit overlaps the st.chat_input widget on an iphone.

  2. issue is compounded by the fact that the Streamlit icon is large and red. So when it is clicked, which is inevitable, it takes the user away from the app to a Welcome to Streamlit page from which the back button no longer works to return to the app.

So the request is, at minimum, enable st._chat_input to be moved up above the fold.
The ideal solution from a usability standpoint is to ditch the logo of find a way to reduce it’s impact on the UX as others have suggested.

IMG_B57819CE8C34-1
IMG_B57819CE8C34-11170×2532 105 KB

1 Like
2

Hi @dvvilkins,

Thanks for posting!

A few questions for you to help us triage this issue for you:

  1. What version of Streamlit are you currently using?
  2. Have you tried any workarounds like changing browsers? If so, what were the results?
  3. Have you noticed this issue on any other mobile devices or just on an iPhone?
3

Hi Tony,

Responses below, but here’s my overarching comment: it would seem to me there is an underlying issue with how page height is being defined for the overall page, which affects every page on stramlit.io (not just the community cloud see below). This latent issue rises to the level of an acute usability issue when combined with the st.chat_input implementation.

First, to answer your questions:

  1. I just put streamlit in my requirements file-- no version
  2. Depending on the phone and browser, the chat input is either at the fold or below it, requiring you to know its there and scroll up, which a user doesn’t know to do and clicks the big red streamlit logo instead and then they are gone.
    drew-chrome-ask_1
    drew-chrome-ask_11170×2532 137 KB
  3. On some platforms the issue is worse. On iPhone 11 Pro iOS 16.5 Safari),there is no way to scroll down to the chat input at all, so the app is unusable.
    gail_safari-ask1
    gail_safari-ask11125×2436 141 KB
  4. I have heard from my users it’s an issue on ipad as well. Not sure what browser.

My Conclusions:

  1. The underlying issue is with the overall html page or container. You can see the bahavior on every page on stramlit.io (see below). The problem becomes acute with st.chat_input implementation. My guess is that it is height settings on the html page or container. It forces a scroll no matter how short the page is (again see example from your documentation below). Then the problem comes to play because chat input seems to be pegged near the bottom of that master container and so gets pulled down below the fold. I’m not a css expert so don’t know the technical terms for these containers. Interestingly, the streamlit logo doesn’t suffer this same fate.
  2. You can see the chat_input issue on other apps:
    https://askchatdummypy-np98ckt3xdpk8bwwymdkmo.streamlit.app/
    https://llamaindex-chat-with-docs.streamlit.app/?ref=blog.streamlit.io

More widely, is the page height issue.
Here’s one from the streamlit documentation that adds scroll to the bottom:

In fact, every page I checked on the streamlit.io domain did this.

Examples of pages that don’t do this:
https://chat.openai.com
https://bigsearchmusic.com

I would encourage you to check this out yourself on a mobile browser and I’m sure you will see what I’m talking about.

4

I am also experiencing this issue which sadly makes the new chat input feature unusable on mobile.

IMG_0BE97C196D3A-1
IMG_0BE97C196D3A-11284×2487 156 KB

IMG_0BE97C196D3A-2
IMG_0BE97C196D3A-21284×2778 205 KB

In my app the input box is completely hidden under the bottom of the screen and a user would have no idea it is there.

If you scroll up to cover the hamburger menu it is pretty well aligned so I wonder if this is more to do with the top spacing than the streamlit logo in the bottom?

Ideally, we’d have exactly control over the placement of the chat input box.

5

Hi @dvvilkins and @revilonz,

Thank you for the detailed responses. Here’s a more similar issue reported on our GitHub issues. Please feel free to add your comments on the issue.

6

I have commented and linked this post on the GitHub issue. Feel free to more comments there and track any changes.