[A little call of attention] Chromium switches

Discussion in 'other software & services' started by m00nbl00d, Mar 10, 2012.

Thread Status:
Not open for further replies.
  1. m00nbl00d

    m00nbl00d Registered Member

    Joined:
    Jan 4, 2009
    Posts:
    6,623
    I usually see what new switches have been added; or when they're removed. I use this link: -https://src.chromium.org/svn/trunk/src/chrome/common/chrome_switches.cc

    If you look for no-referrers, you won't find it there. So, sometime ago I removed that switch from my batch file. I then started to use the extension ScriptNo, which didn't work quite well with Chromium builds.

    So, I was looking for info that could point to clues that pointed the reasons why no-referrers was removed.

    This is actually embarrassing, because I'm familiar with the following link, but I always thought it was the same deal as the above link. :oops:

    -http://peter.sh/experiments/chromium-command-line-switches/

    In this link, you'll see that no-referrers is there. In fact, I just re-added it to my batch file and went to Dshield test page, where one can check the browser header -https://secure.dshield.org/tools/browserinfo.html

    It is working. I actually should have made that test before deleting the switch, back then. :D

    Just in case you also believe this or that switch was removed, it may have not been removed.

    I wonder why -https://src.chromium.org/svn/trunk/src/chrome/common/chrome_switches.cc lacks, at least, no-referrers? o_O

    This is why one shouldn't put blind faith on anything. Lesson learnt. :ouch:
     
  2. Hungry Man

    Hungry Man Registered Member

    Joined:
    May 11, 2011
    Posts:
    9,148
    I usually go by Peter's. I've seen plenty of Chromium information pages that aren't completely up to date.
     
  3. vasa1

    vasa1 Registered Member

    Joined:
    May 1, 2010
    Posts:
    4,152
    I've always liked the way he presents the switches. AFAIK, he's been an official Googler for a while now.
     
Loading...
Thread Status:
Not open for further replies.