125
26
When I want to configure an addon, for example Ghostery, the tab shows a URL like this one:
chrome://ghostery/content/options.html
What does it mean? Does it have something to do with the Chrome browser?
125
26
When I want to configure an addon, for example Ghostery, the tab shows a URL like this one:
chrome://ghostery/content/options.html
What does it mean? Does it have something to do with the Chrome browser?
178
The phrase chrome
has been used by Mozilla since long before Google Chrome came on the market. Typically the phrase "Chrome" referred to all the area around your viewport, but not the viewport itself. Sort of like the chrome plating some cars have around their windscreens or headlights.
See here for more details - but no; nothing to do with Google Chrome.
22
This is a type of binding in firefox that has existed for some time. Chrome refers to the user interface of the browser. For instance this includes everything outside of the webpage you're viewing.
The chrome:// binding is a feature for developers of extensions and built in Firefox features such as the bookmarks manager or downloads window. You can find a list of these chrome:// mappings here. Basically it is a way for firefox to reference files that are on your computer that however might change due to your install path, operating system, or simply the firefox developers choosing to change the physical folder path. These bindings allow developers to always reference the same location.
There are also some other advantages or differences for developers as outlined here. They include the ability that chrome:// url's are exempt from security restrictions - so they can do more things and interact with your browser. They allow the feature to interact or reference other user parameters that might have changed due to customization of themes or locals (regional or language changes) without having to know exactly what the user's customized settings are.
The fact that Chrome was named after the same type of 'chrome' as the FF scheme was, is useful in clearing up any remaining confusion in light of Mark's answer. It makes an odd coincidence somewhat less mystifying. Thus, I fail to understand why one would choose not to include this fact in an answer to the question asked. – lukeuser – 2018-07-17T00:11:45.290
43Actually a lot to do with Google Chrome: Google Chrome is explicitly named after the user interface chrome of a browser. In their very first marketing video (or was it the comic?) they explain something along the lines of focusing on reducing the chrome and focus on the content instead or summin’ like that. – Konrad Rudolph – 2012-12-10T08:10:39.167
22
(Page 24 of the comic)
– Konrad Rudolph – 2012-12-10T08:17:53.21780I beg to differ, although the name of Google Chrome is named after the UI component, the
chrome
part of FF has nothing to do with the chrome browser itself; as the op is obviously asking. – Mark Henderson – 2012-12-10T09:47:37.13329I didn’t intend to comment here again but the sheer number of upvotes on your comment surprises me: I mentioned that Google Chrome is named after the UI concept. Clearly this implies that
chrome://
, which refers to the UI concept as well, doesn’t in fact refer to the Google Chrome browser. At least I thought that was obvious. Now, that isn’t the same as “nothing to do with x”. “nothing to do” implies that there’s no connection – and that’s wrong, there is a connection: bothchrome://
and the name of Google Chrome refer to the same UI concept. – Konrad Rudolph – 2012-12-10T16:06:07.293… And as such my comment merely served as an additional information about the origin of the name Google Chrome. – Konrad Rudolph – 2012-12-10T16:07:18.480
10Does anyone else find it odd that Google named Chrome after what they are trying to reduce? Maybe they should have called it Chro! – George Duckett – 2012-12-11T08:35:52.350
12@Konrad: I see what you're saying, but I think you may be mistaken in thinking that the "has nothing to do with" relation is symmetric. In other words, it is plausible that while the name of Google Chrome has something to do with the chrome:// pseudoscheme in Mozilla, the reverse is not the case. – LarsH – 2012-12-12T02:13:08.943