Routing and renaming of chrome:// url..

[Vane]

I am trying to change the "chrome://" text to "name://" which appears in the omnibox when a corresponding page is visited for ex: "chrome://settings" to "name://settings".

I noticed that specific urls like "chrome://resources" , chrome://theme" play a huge role in managing the static resources like .css and .js file, changing them without any errors is difficult that's where I am confused....

How and where should I make changes in chromium source to have name://resources recognized without violating Content Security Policy, and I am bit confused about some of the chrome urls like "chrome://print" which are used internal purposes and side panels etc, I think, what should be my approach to make this work properly.

Can you help me :)) ?

[Demetrios Papadopoulos]

See similar discussion at https://groups.google.com/a/chromium.org/g/chromium-dev/c/yrLCH72lLOg/m/PpFLYWmbAgAJ. In short, you would need to change a ton of places across the codebase for this to work (basically everywhere where "chrome://" appears).

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/8d97c0ce-89d3-4d3f-9ec5-05b8d4bc7f5cn%40chromium.org.

[PhistucK]

By the way, if you go to chrome: URLs when using Edge, they still go to those pages, but the address bar shows an edge: URL. To me, it means they might be mostly changing the URLs the user might see rather than changing all of the chrome: URL references. Although it is possible they simply have a blanket redirection/rewrite of chrome: to edge: to ensure power user familiarity or to make sure accidental chrome: references still go to the intended target.

☆PhistucK

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAPUSrA3q22_1mNkXd1w2gZ9kaqA_ogdbtiXnQJAK5JjzjVOdHQ%40mail.gmail.com.

[guest271314]

What does Content Security Policy have to do with the question? What are you really trying to do, and why?

[Vane]

https://groups.google.com/a/chromium.org/g/chromium-dev/c/SmdFcRNBIbQ/m/mFHaVlaNAQAJ

I saw this post and am trying to implement these steps to achieve chrome:// to name:// .
I tried changing status_bubble omnibox_edit_model webui_url_constants url_util url_constant chrome_browser_main cc files but not getting results can you help me understand the changes to files required to accomplish this task.

[PhistucK]

It depends on what you are trying to do, really change the protocol from chrome to name, or just to show the user as if you changed it?

For the latter, it is just about displaying stuff, so the omnibox files and the status bubble files might be enough, as well as some blanket redirector of name: to chrome: somewhere (maybe search for whatever it is that already does that for about: to chrome: redirection).

Hopefully you are using source.chromium.org to easily search and cross-reference the code base.

☆PhistucK