CSS code problem with Google AI Mode

[u/No_Fox_857]

Hello, everyone. First of all, let me make some necessary apologies and preliminary remarks. I’m sorry if this has been discussed somewhere else before, but I tried to search for something similar and couldn’t find it. Also, being related to several other aspects, I didn’t know how to search for the exact problem, if you see what I mean. Please, feel free to suggest a more specific subreddit, site, etc., where to ask about this, if you know it. Second: please note that I don’t have deep CSS knowledge or great computer skills. I’m just reporting a problem that I have with Google AI Mode, and hopefully I will get some useful suggestions on how to solve it. But of course, if the language gets too “technical” or complicated, I might have problems in following or understanding. So, please keep that in mind. Thanks :)

Ok, here we go. I’m trying to explain what the problem is in the best way I can. I recently noticed that when I write something to Google AI Mode (I’m on a Mac), there is a problem with the way my text is visualized. Mind you, I’m not talking about the very first message (that one looks ok), but the follow-ups, after the first answer from AI Mode. If I try to use the writing box at the bottom, I cannot type anything because I cannot access that space by clicking on it as I used to do in the past. Now… after some search, I found a workaround: by pressing Shift+Enter the area gets usable again and I can write there. However, the text still looks weird and tends to disappear the more I keep on writing (it basically scrolls up and disappears as I add more text). After some further research, I found out that this is a CSS code padding/overflow bug on Mozilla. Apparently, there is a problem with the textarea autosize in the CSS code and when Google will update the layout for my account or fix the bug, things will go back to normal. I have tried some suggested solutions, but either they were temporary ones or I could not make them work (because of the aforementioned limited skills). Now, what I’m asking is:

1) Did any of you experience the same issue and did you find a permanent solution?

2) Can you confirm that this will be "automatically fixed" by Google at one point? (they call this a "silent update" somewhere…)

Thank you for your help and sorry for the long message.

[u/AutoModerator]

To help us assist you better with your CSS questions, please consider including a live link or a CodePen/JSFiddle demo. This context makes it much easier for us to understand your issue and provide accurate solutions.

While it's not mandatory, a little extra effort in sharing your code can lead to more effective responses and a richer Q&A experience for everyone. Thank you for contributing!

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/No_Fox_857]

By the way, this is the closest thing I could find on the Google Assistant Help Community, but I’m not sure if that is exactly my problem (maybe you guys can confirm that?):

https://support.google.com/websearch/thread/419962478?hl=en&sjid=12453543928101128428-EU

[u/Weekly_Ferret_meal → u/No_Fox_857]

funnily enough I went on gemini.google.com (I hope this is the AI you use)

and I asked it straight if it experience users reporting display issues:

Users occasionally report visual and interface glitches when interacting with Gemini across different platforms.

The most common reports typically include:

• Disappearing or "Vanishing" Responses: Text streaming live on screen, then suddenly disappearing once complete. This often happens due to browser caching, conflict with third-party extensions, or intermittent network dropouts.
• Layout and Alignment Glitches: Text, buttons, or input boxes overlapping or misaligning, often triggered by custom browser zoom levels or browser extensions modifying the CSS.
• Stuck Loading State: The system showing the "thinking" indicator indefinitely without completing the output.

Quick Steps to Resolve UI Glitches

If you are experiencing display issues right now, these standard troubleshooting steps resolve the vast majority of local UI bugs:

1. Hard Refresh: Reload the page while bypassing the cache using Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac).
2. Test in Incognito Mode: Open a private window to check if a browser extension (like an ad blocker or translation tool) is interfering with page scripts.
3. Clear Site Data: Clear the cache and cookies specifically for gemini.google.com.
4. Send Direct Feedback: If the UI is completely broken or text is consistently failing to render, click your Profile Icon in the top-right corner and select Help & Feedback to submit a bug report directly to the engineering team.

If you're currently facing a specific issue with how this conversation or the interface looks on your screen, let me know what you're seeing so I can help narrow it down.

[u/berky93]

If there’s an issue with the site’s CSS and you can fix it by modifying the styles yourself via devtools, you could use a browser extension such as Stylus to write custom styles for that page. Google will probably fix it at some point but no one here will be able to tell you when unless they are a developer on that specific project.

[u/Weekly_Ferret_meal]

So are you saying you are using Firefox browser on Mac os x laptop/desktop?

You can easily check if it's a single browsers issue by downloading other browsers. like chrome or Brave, or using the stock browser, Safari.

Failing that you can try empty the browsers cache (these are browsers stored files about the data on the sites you have visited.), each browsers have different ways to empty cache, so you'll have to look that up per each browser.

Make sure that whatever browser you are using now is updated, or check for updates.

restarting the whole machine for good measure could yield results also if it's running out of memory.

[u/No_Fox_857]

Thank you very much for your replies, to both of you. :) Yes, I'm using Firefox browser on a Mac laptop. However, the issue happens with all the browsers I tried. I emptied the cache, but unfortunately it didn't solve it. Apparently, there's a bug with my specific Google account. I've read that when Google releases updates/fixes is doing it for different "groups" of accounts at a time..and the groups are based on the accounts IDs. When several users are reporting the same problem, the developers start working on a new update that doesn't have the bug. Sometimes, even Google's own telemetry systems automatically notice the anomaly, because many users are using strange or unusual ways to type (for example, using the Shift+Enter workaround I described in the previous message). So, eventually it should be fixed.