remove ssui from safe search query
Reported by
pdk...@gmail.com,
Apr 2 2016
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.110 Safari/537.36 Steps to reproduce the problem: 1. Enable ForceGoogleSafeSearch 2. Use Google What is the expected behavior? Safe Search is enforced. What went wrong? Safe Search is enforced, but it also adds a background image to the Google Search header, which ironically makes the text (confirming that Safe Search is active) barely legible. (And I'm sure it does not adhere to recent Google design standards.) Did this work before? N/A Chrome version: 49.0.2623.110 Channel: stable OS Version: Ubuntu 14.04 Flash Version: From what I can tell, it has no effect other than adding the image. // Google SafeSearch query parameters. const char kSafeSearchSafeParameter[] = "safe=active"; const char kSafeSearchSsuiParameter[] = "ssui=on";
,
Apr 4 2016
I don't think it's a server issue as the parameter is set by Chrome.
,
Apr 5 2016
Yes, but the guidance from server folks is that we are supposed to pass that parameter up. I understand that your analysis shows that "it has no effect other than adding the image", so it may be obsolete, but we need to hear back from them before we remove it.
,
Apr 6 2016
Thanks for the explanation, I understand now. Just another point: when you enable Safe Search manually on Google, through the settings cog, the image is not displayed, only the text. It appears to be a relic of past times.
,
May 29 2016
(Any update from Googlers?)
,
Sep 4
not sure if ssui is needed any longer - probably makes sense to talk to the safesearch folks to confirm.
,
Dec 11
,
Jan 2
,
Jan 3
#8: Was this addressed on the server side? Regarding https://chromium-review.googlesource.com/c/chromium/src/+/1391686 : Has it been confirmed that this parameter can be safely removed without breaking anything? I don't see any updates on the internal issue (b/27992913).
,
Jan 4
,
Jan 8
What we just did was test that things worked without the ssui= parameter, and removed it, which is consistent with how google behaves if you manually turn on safesearch. I now updated that bug to ask whether there was any issue in removing ssui= and what it does. Thanks, Guido |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by atwilson@chromium.org
, Apr 4 2016Status: Assigned (was: Unconfirmed)