Firstly, I think this is unlikely to happen since it would involve a fairly large amount of churn across the codebase (there are too many references of chrome://, chrome-untrusted://, chrome-extension://). Secondly, AFAIK the "chrome" part in "chrome://" does not actually refer to the "Google Chrome" product name. Note that Firefox also has several "chrome://" URLs (see
here). Instead it refers to anything that is not part of the web contents, aka it is part of the "chrome" of the browser, in the literal meaning of the word "chrome" as some "finish" layer around something else, in this case around the "web contents".