Visiting chrome:dino does nothing |
||||||||
Issue description<b>Version: <Kenneth, what is the frequency?></b> <b>OS: <please tell me it's not XP></b> What steps will reproduce the problem? (1) Type chrome:dino into address bar. (2) (3) What is the expected output? Dinosaur game. What do you see instead? Error that the site can't be reached. (We shouldn't say "site can't be reached" for about: or chrome: URLs anyway). Please use labels and text to provide additional information.
,
Nov 7 2016
I think this is expected behavior?
,
Nov 7 2016
Not expected behavior :) I filed the issue since I felt that there should be a way to get to the game without invoking the error page, and it seemed that others shared the sentiment. chrome:dino is a strawman. Let's wait and see if edwardjung@ has an opinion on whether this is something desirable or not.
,
Nov 7 2016
@mmenke - internal G+ post for context https://plus.sandbox.google.com/u/0/103403756042232855596/posts/Ybnn7uYRTWk?sfc=false I'm not opposed to having this, but is it any easier than just going offline and reloading a page, especially on mobile. For those who don't like going offline, maybe. If the intention is to make the game easily accessible then I think there are better ways. It was always done as an easter egg rather than actual feature so the discoverability level is intentional. If we're moving it into a feature and marketing it as such then maybe it's time to change the entry point UI on the network error page itself. It could be it's own suggestion in the try list for example. We can them promote is a 'distraction' while you wait for network connectivity to be restored.
,
Nov 10 2016
Moving to Available for the crass purpose of getting it off the network bug triager's radar screen. This sounds like it'll happen if someone jumps on it and not otherwise, which fits with "available" as a state--the priority's pretty clear from the bug and the linked G+ thread.
,
Nov 10 2016
The URL in #1 is incorrect. The correct URL is chrome://network-error/-106 Either way, I'll mark this as WontFix because: * There's a way to get to the game using a chrome:// URL without disconnecting from the internet. * Determined users can discover how to get there. * If we want to market the Dino game, then we need something better than a chrome:// URL.
,
Nov 10 2016
I don't feel strongly enough to reopen, but I _wrote_ the code to add about:about, and I know a lot about Chrome. I still couldn't determine how to get to this page, when I tried, for a half hour, the other night. So I disagree with "Determined users can discover how to get there." I don't think this is about "marketing" so much as "fun". I don't think it would be inappropriate to add a simple about:t-rex URL, linked from about:about, that merely resolves to the error link you give above. So IMO, it would be reasonable to reopen.
,
Nov 11 2016
re:#7 Sounds reasonable to have a more reachable URL that exists in the auto complete and chrome:// pages list. I'll put together a CL today.
,
Nov 11 2016
#7: I see that the "chrome://network-error/-106" URL is mentioned in several blog posts, forum posts and StackOverflow questions, but I only got to them because I searched for the URL. It's pretty difficult to discover otherwise. So yes, 'determined users can ...' was too optimistic. #8 thanks!
,
Nov 11 2016
As long at this doesn't interfere with the whole "your dino game has been blocked by your administrator" deal, but I think that code for blocking the game is on the page.
,
Nov 11 2016
That's right, it's just an entry point. The admin policies are enforced on the page.
,
Nov 11 2016
fwiw: I just double-checked that https://www.chromium.org/administrators/policy-list-3#AllowDinosaurEasterEgg works on chrome://dino
,
Nov 11 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/8d968d89bd70b82af787d1a04dd915a006e59dbf commit 8d968d89bd70b82af787d1a04dd915a006e59dbf Author: edwardjung <edwardjung@chromium.org> Date: Fri Nov 11 18:34:31 2016 Add chrome://dino short URL to link to the internet disconnected network error interstitial BUG= 662661 Review-Url: https://codereview.chromium.org/2498663002 Cr-Commit-Position: refs/heads/master@{#431604} [modify] https://crrev.com/8d968d89bd70b82af787d1a04dd915a006e59dbf/chrome/common/url_constants.cc [modify] https://crrev.com/8d968d89bd70b82af787d1a04dd915a006e59dbf/content/browser/webui/url_data_manager_backend.cc [modify] https://crrev.com/8d968d89bd70b82af787d1a04dd915a006e59dbf/content/public/common/url_constants.cc [modify] https://crrev.com/8d968d89bd70b82af787d1a04dd915a006e59dbf/content/public/common/url_constants.h
,
Nov 11 2016
Yay! Fixed?
,
Nov 14 2016
Now shipping in Canary / Dev. Should be stable M56. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by asanka@chromium.org
, Nov 7 2016