4 ms·
That's the way I read it too and I'm surprised no one else has mentioned this. Unless I'm missing something Google is allowing XSS for their own domains in chro
by johnward 12y ago
That's the way I read it too and I'm surprised no one else has mentioned this. Unless I'm missing something Google is allowing XSS for their own domains in chrome.
- gcb0 12y agoyes. and much more. for example, even when using open source web kit or chromium they actively removed all options to disable referrer. go on. try to find it on your current chrome build. or even on chromium thanks to their legacy. then remember that referrer with its most exposing setting is required for Google to monetize both their organic and paid search.
- lkbm 12y agoThe only way to do it in Firefox is through the scary and arcane about:config (or an extension). Historically, methods to remove that have not been provided by browsers, whether Google-developed or not. I've always done it via Privoxy, never the browser.
- gcb0 12y ago> scary and arcane i use it every day. even on firefox mobile! and it serves my purposes just fine. not to mention you are not exactly right. as you can update those values via user scripts that can be easily distributed or even made as an extension that change those values for you and/or provide a new settings controller UI.
- lkbm 12y agoYeah, and I use the command line every day. Whenever people see it on my screen, they think I'm "hacking". There are Chrome extensions to do it as well. The point is, the lack of a UI control usable by the average user is not some Google conspiracy. It's always been the standard in pretty much all browsers.