4 ms·
The extension ID is literally hard coded in the code of the scheme hiding code. https://source.chromium.org/chromium/chromium/src/+/master:chrome/browser/ui/too
by marksomnian 6y ago
The extension ID is literally hard coded in the code of the scheme hiding code. https://source.chromium.org/chromium/chromium/src/+/master:chrome/browser/ui/toolbar/chrome_location_bar_model_delegate.cc;l=46?q=jknemblkbdhdcpllfgbfekkdciegfboi&sq=&ss=chromium&originalUrl=https:%2F%2Fcs.chromium.org%2F https://source.chromium.org/chromium/chromium/src/+/master:c...
- andrewprock 6y agoHow a proprietary extension can get preferential features illustrates that chromium is open source in name only.
- shadowgovt 6y agoHardly. If you look at firefox's source, you will find several extensions that are hard-coded for special handling. This is not new.
- andrewprock 6y agoTrue, but the distance between Firefox source and Firefox is config+compile. You cannot compile Chrome. I've heard that Chromium can be compiled and run, but I've never actually seen it, or hear of anyone using that professionally.
- shadowgovt 6y agoI'm not sure what your point is... You thought it was weird that an extension would get preferential treatment, and I pointed out that this is true for Firefox also.
- andrewprock 6y agoMy point is that you are correct. There are other factors at play which mitigate the preferential treatment, but it's definitely there in Firefox as well.