Omnibox search while offline shows unfriendly error page |
|||
Issue descriptionChrome Version: 66.0.3356.0 OS: Android What steps will reproduce the problem? (1) Go offline or be on a flaky connection (2) Type a search term into the Omnibox (e.g., "go pro") What is the expected result? Since I am offline, I would expect to see an Offline Dino page, the same as if I had typed a URL into the omnibox. What happens instead? I see the error page: "This site can't be reached ... The webpage at https://www.google.com/search/.... might be temporarily down or it may have moved permanently to a new web address. ERR_FAILED" There are several problems here. (1) This is not a helpful error message. I am offline (in airplane mode in this case). It is not the case that Google is "temporarily down" or "moved permanently to a new web address". (2) I would rather get guidance such as the ability to perform the search later or look at offline pages, etc. rather than a generic error message. (3) Since this is an Omnibox search, I believe we can provide a better, more friendly error UI. Perhaps something with a Google logo or some indication that you may be offline. Showing the full Google search URL is really unfriendly. I would be willing to bet good money that a lot of errors seen by users are from flaky network connections while performing omnibox searches, so we might want to prioritize work on fixing this.
,
Mar 8 2018
I suspect collinbaker's fix is not the problem here, since all his work was behind the offline pages renovations flag. Also, since this was his intern project, he's not at Google to answer your questions. The bug seems to mostly be an issue with the intent and design of the error page, aboss@chromium.org is likely the best owner for that.
,
Mar 12 2018
Note: does not repro on Mac osx with Chrome 64. The dino page is shown. catherinechung@google.com, do you think this could be related to the change at https://chromium-review.googlesource.com/c/chromium/src/+/549074 If not, feel free to send this back to me or to my second guess, which is the change at https://chromium-review.googlesource.com/c/chromium/src/+/579188.
,
Mar 14 2018
Hm I'm also unsure as to why this specific error is being triggered instead of our offline dino. edwardjung@ in case he knows more about the triggering |
|||
►
Sign in to add a comment |
|||
Comment 1 by nyerramilli@chromium.org
, Mar 8 2018Components: UI>Browser>Offline
Labels: FoundIn-66 Target-67 FoundIn-67 M-67 Needs-triage-Mobile Triaged-Mobile FoundIn-65 hasbisect