Posted: Wed May 26, 2010 2:07 pm Post subject: Update search box on webpages
FYI. Google recently enhanced their Google Custom Search to support their autocomplete feature, I have enabled Google's new autocomplete feature in the search box at the top of all main website, Trinity, and NeoWiki pages.
Please let me know if you see any broken search boxes on any of our pages.
One thing I noticed (and it's really minor, though I think you fixed it before for the old search) is that the browser's "lock" icon shows up unlocked when you're logged in, i.e. there's some content related to the search field that not being served over SSL.
Before I think maybe it was the image, but that doesn't seem to be the case now; I'm not sure what it is.
Otherwise, I've noticed nothing amiss.
Smokey _________________ "[...] whether the duck drinks hot chocolate or coffee is irrelevant." -- ovvldc and sardisson in the NeoWiki
One thing I noticed (and it's really minor, though I think you fixed it before for the old search) is that the browser's "lock" icon shows up unlocked when you're logged in, i.e. there's some content related to the search field that not being served over SSL.
That is old sad limitation of Google's updated search box. Some of the URLs that it fetches (e.g. the image and the autocomplete list) are hardcoded to fetch over HTTP. That is what triggers Firefox to have an exclamation point over the "lock" icon.
Unfortunately, Google's search box now dynamically downloads the JavaScript that does the HTTP fetching despite the fact that our pages fetch the initial Google JavaScript files over HTTPS. In other words, I can no longer remove the HTTP stuff like I did before.
Surprisingly, only Firefox and IE have a problem with this but Safari considers the page to still be fully locked.
Unfortunately, Google's search box now dynamically downloads the JavaScript that does the HTTP fetching despite the fact that our pages fetch the initial Google JavaScript files over HTTPS. In other words, I can no longer remove the HTTP stuff like I did before.
Thanks for the explanation. Sad to see Google roll out something half-baked like this at the same time they're trying to make a big splash by offering google.com searches over HTTPS
Smokey _________________ "[...] whether the duck drinks hot chocolate or coffee is irrelevant." -- ovvldc and sardisson in the NeoWiki
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You cannot download files in this forum