Links of the bottom of the "Advanced Search" page are on top of the select boxes
In that position the bar of links "Google Main Page Ad programs Business Solutions Privacy and... Everything About Google" covers the select box at that position (either "domain or website" or "language" or "region" etc.).
If I push the lower margin of the window upwards making the window smaller, the bar of links moves upwards uncovering the select box hidden under it and covering another select box further up. I can go all the way up till it covers the text boxes "all these words" or "exact sentence". I have uninstalled Firefox and installed a new Firefox. I eliminated all cookies and caché. I disabled all plugins. I restarted and I also opened in safe mode, but it keeps happening.
All Replies (8)
I get the same result on my Firefox. It looks to me that the Google Advanced Search page has not been properly tested with Firefox at different screen resolutions.
You can test different resolutions in Firefox using Responsive Design View.
At the bottom of a standard google search page is a 'Send Feedback' button. I think that would be the best place to bring this to Google's attention.
Note that there are also changes made on purpose via @media CSS rules that hide the examples below a specific width:
@media (max-width:1056px){ div.cell-header-comment{ display:none !important } div.cell-query-example{ display:none !important } div.cell-example{ display:none !important } }
Modified
My "Advanced Search" page does not have a "Feedback" link, I have to do a search to find it and then, obviously, the screenshot accompanying the feedback does not correspond. But still, I sent them the feedback. As this also happens with Chrome it clarly is a Google bug not a Firefox bug.
For those that don't understand what we are talking about I've left a screenshot (Spanish version)
Looks that this is caused by setting the height of the div.bottom-wrapper to 100% and that causes the div.bottom-links-wrapper to appear at the wrong position (i.e in the middle of the page).
If I disable the height: 100% !important rule (why even an important flag?) with the Style editor (Inspect Element) then the page appears correctly.
div.bottom-wrapper{ min-height:100%; margin:0 auto -60px; height:auto; height: 100% !important }
This rule in userContent.css or Stylish should fix this.
@-moz-document domain(www.google.com){ div.bottom-wrapper { height:auto!important; } }
The customization files userChrome.css (interface) and userContent.css (websites) are located in the chrome folder in the Firefox profile folder.
Yes, I also assume the effect is a CSS problem, however most Google users (99.99%???) are not fluent with code editing, so I wouldn't expect the majority of users to edit a css file.
I would like to know which is the cause for this to happen. Considering this has happened repeatedly although I have downloaded a new version of Firefox and it also happens with the last version of Chrome, I suppose the problem is in Google Search webpage or it has a bug that gets a short-circuit when used with those browsers.
Should Google modify something in its webpage or is there a user-friendly fix. CSS might be developer-friendly, but not user-friendly.
BTW, the same Google search problem can happen with IE.
I am wondering if this used to happen before and I didn't notice it (highly improbable because I do all my searches with Advanced Search, and I must do some 100 searches per day at least) or this is something that is just happening all of a sudden?
I believe Google need to modify the CSS on their side. The page must have been updated at some stage and a mistake was made.
Until that is done you can use cor-el's rule to force the page to display correctly on your own version of Firefox.
Thanks eddyc for confirming my suspicion.
Yes, I think cor-el's rule is a good option, however I think I'll leave Firefox, Chrome or IE in peace. Now that I know that moving that links bar with the bottom margin of the window I can uncover the text-box or select-box I want to use. At least the problem doesn't affect functionality.
Thanks everyone for your comments and specially cor-el for taking the time to find a fix. Hopefully Google developers will listen in.
Modified