0

Is it possible that we could support the internal chrome:// URLs used by Google Chrome and Chromium? There are many questions where one has to access an internal page used by Chrome to solve the problem. For example.

  1. Why is chrome://settings and chrome://plugins broken?
  2. Is there an "about:config" (Firefox) In Google's Chrome?
  3. How do I install a crx file on Google Chrome Dev?

While this is a minor annoyance, it is still frustrating every time I happen to encounter it. Plus, there's no harm in allowing it so why prevent it?

By the way, can we also support the about: style links used by Firefox?

1

The only whitelisted and supported URI protocols are http, https and ftp.

All other link protocols go through the Markdown sanitising wash and removed.

Besides, you can't click those links anyway.

  • I'm reading that other post (thanks for finding it, search on SE sucks =/), but what was Code Grey's security concerns? – user137430 Jul 8 '12 at 2:32
  • Create an HTML page on your machine with such a link. And then try and click on it. See where it takes you. – random Jul 8 '12 at 2:37
  • Ah. So the reason is that Google Chrome actually doesn't follow chrome:// links? – user137430 Jul 8 '12 at 2:41
  • That's the security concern. Google Chrome won't let you get yourself in trouble by clicking on such links where it hasn't generated them itself – random Jul 8 '12 at 2:43
  • Okay, thanks for answering a duplicate. =P I just couldn't find it via SE or Google. – user137430 Jul 8 '12 at 2:44

You must log in to answer this question.