iOS - Google Search Window Disappears Behind Safari Address Bar

After the latest iOS update version 16.1 (20B82), when I use Safari to access Google, as soon as I tap into the search window, the search window disappears behind the Safari address bar at the top of the screen, so I can’t see what I’m typing. Seems like a bug, because it did not use to do this. Is any one else having this problem?

iPhone 14 Pro, iOS 16

Posted on Nov 6, 2022 1:29 PM

Reply
Question marked as Top-ranking reply

Posted on Mar 6, 2024 4:24 PM

I think I found a fix for this. Go to Settings->Safari and scroll to the bottom where see “page zoom”. Mine shows setting for Page Zoom on “google” and seprste settings for “other websites”. Google was set to 115%, I change this to 100% and problem solved.

Note I am unsure why it showed Google as a separate option from all other sites, possibly because I was on that site when I went to settings.

243 replies

Dec 11, 2022 5:51 PM in response to Dileer

I did turn off Java but yes. It’s used so much for webpages, it’s moot to turn it off. Short of placing the address bar at the bottom (which I don’t like), there’s not other way I have found to fix this. It seems like a simple fix on apples part but for some reason, this is not being addressed by them. Frustrating.

Dec 11, 2022 7:13 PM in response to Ulin27

I took off the Java Script and it all seemed different. So I’m back to where I was before. With the search bar at the top hidden. I literally have to use my microphone to search on something. I don’t want it at the bottom either. I would like Apple to tell us what the problem is. Are we the only people in this group that have this problem? I find that hard to believe. I guess we have to wait. I tried switching it to chrome, but the problem still exists.

Feb 9, 2023 4:32 PM in response to whydavewhy

This bug still hasn't been properly fixed. I still have this problem when it's zoomed in. I like having Google zoomed in 115% to help me prevent tapping the wrong thing but this bug is really annoying.


Another problem is it jumps down too much after pulling down and tapping the box a second time so there's unnecessary white space above.

Jan 16, 2024 10:21 AM in response to _SusanB_

—SusanB_

Yes, I posted last week, or just before maybe, that it appeared to be ‘working’ again, or at least, wasn’t requiring a re-scrolling down of the page each time.

However, what I have noticed since, is that even after you tap in the Google search bar, the screen change, the search text field moves to the top but, vitally, still visible, and it shows a list of your previous searches below that.

BUT YOU STILL have to click into the search text field at the top to get it to accept input.


All I can think is that the people behind the page code for this don’t care less about its compatibility with different, non-Google browsers and haven’t bothered trying to test it on same.


It annoys the crap out of me though that Apple haven’t made any comment one way or the other. Zilch, Nada. So we, as (assumption here) valued users, have absolutely no idea if Apple even:

  • knows anything about this issue when occurring in the first place
  • knows how bloody annoying it is to users when this isn’t working
  • acknowledges that this is ‘a thing’
  • has it on any kind of list at all, let alone a list of ‘future changes’ or ‘investigations’


i would dearly love it if Apple were to maintain a list of user reported issues, containing all the various steps / statuses that they will go through. Even if 99% of them end up under the “KNOWN BUT NO ACTION TO TAKE” status.

That is how to let your customers / end users (those people that will be opening their wallets every September) know that they, and their intelligence and views, are valued.

Any reasonable customer recognises that it’s totally unreasonable for Apple, or any tech company for that matter, can, or has an appetite to, address everything.

If I felt confident that Apple were aware and acknowledged that this problem existed for some users, but had made the decision that it didn’t effect sufficient numbers of them, it was too costly to fix for the given priority/importance, then I, and pretty sure everyone else, would soon stop wasting my time and mental processing cycles, writing on this forum thread, and any others, about various ideas for root causes, solutions or workarounds, or rants, like this one.


Of course, what tech company would dare to openly admit that there was problems? And what tech company would dare to give a transparent view of line items in its problem management process to its users?


Maybe this small band of the faithful are the only ones affected by this. Perhaps we are living in an obscure bubble, taking about things that no one else out there recognises, in a language that no one else understands?

Jan 16, 2024 10:33 AM in response to TheBionicGolfer

Thanks. I was a database admin/tech support rep for years so I broke it down and tried to figure out. While it's speculation it makes sense to me anyway, that the page may display differently and Google isn't going to change their code to correct an Apple problem. I'm giving up though on the thought of it getting fixed. Not sure where the error actually originate from but neither Apple nor Google will take ownership of this one so I think we are out of luck. I am just going to use Chrome going forward since Google is my home page and search engine of choice.

Jan 16, 2024 10:38 AM in response to TheBionicGolfer

—SusanB_

Yes, I posted last week, or just before maybe, that it appeared to be ‘working’ again, or at least, wasn’t requiring a re-scrolling down of the page each time.

However, what I have noticed since is that

  • after you tap in the search bar on the Google front page the screen then changes
  • the search input text field moves to the top of the screen but is, vitally, still visible,
  • you are presented with a list of your previous searches below
  • there is NO FLASHING CURSOR in the search text field


YOU STILL have to click into the search text field at the top to get it to accept input.


All I can think is that the people behind the page code for this (Google or Apple) don’t care less about its compatibility with different, non-Google browsers and haven’t bothered trying to test it on same.


It annoys the crap out of me though that Apple haven’t made any comment one way or the other. Zilch, Nada. So we, (an assumption here) as valued users, have absolutely no idea if Apple even:

  • knows anything about this issue occurring in the first place
  • knows how bloody annoying it is to users when it happens, especially if, like me, you’re an avid and continuous user of Safari and Google search
  • has acknowledged that this is ‘a thing’ or an acknowledgement of any kind
  • has this ‘thing’ on any kind of list at all, let alone a list of ‘future changes’ or ‘investigations’


i would dearly love it if Apple were to maintain a list of user reported issues, containing all the various steps / statuses that they will go through. Even if 99.99% of them will end up under the “KNOWN ABOUT - NO ACTION NECESSARY OR PLANNED” status.

That is how to let your customers / end users (those people that will hopefully be opening their wallets every September, enabling higher bonuses for all, and more expensive presents under the Christmas tree) know that they, and their intelligence and views, are valued.

In this day and age any, reasonable, customer recognises that it is, of course, totally illogical to expect that Apple, or any large tech company for that matter, can, or has an appetite to, address everything reported by its end users.

If I felt confident that Apple were aware, and acknowledged, that this problem existed for some users, but had made the decision that it didn’t effect sufficient numbers of them, or it was too costly to fix for the given priority/importance, then I, and I’m pretty sure everyone else reading this, would soon stop wasting my time, and mental processing cycles, writing on this forum thread about various well thought out ideas for potential root causes, solutions or workarounds. Or, indeed, rants, like this one maybe?


Of course, what tech company would dare to openly admit that problems with their products existed? And what tech company would dare to give a transparent view of line items in its problem management process to its users?


Maybe this small band of the faithful are the only ones affected by this. Perhaps we are living in an obscure bubble, discussing things that no one else out there recognises, in a language that no one else understands?

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

iOS - Google Search Window Disappears Behind Safari Address Bar

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.