Carl

@uazo I will pick up from this and release it; then I will check whether to skip some versions or not.

This is probably due to the [patch that reduces referrer granularity on cross-origin transitions](https://github.com/bromite/bromite/blob/105.0.5195.147/build/patches/Remove-HTTP-referrals-in-cross-origin-navigation.patch); @uazo the preference value seems unused, is that on purpose?

> first of all, welcome back @csagan5! I have not gone anywhere? > the flag you signal has always been present in chromium I understand, so it works automatically because...

> > when upstream rolls out the change to a larger percentage of users. > > this particular one I think never Care to elaborate? > maybe privacy-related changes should...

> Of course! it is possible to give the user a choice, adding a new preference is simple and has no impact on maintenance @uazo why can't it be left...

> I try. I don't think that blocking referrers to third parties will ever be the default, because all the necessary tools to block them (norel attributes, http headers, meta,...

To go back on topic, for this issue we should probably: * add another preference near the existing one (to respect what the W3C standard says: the user agent allows...

> > why can't it be left as it was before? I am against adding a preference for every possible combination. > > I apologise, I get carried away by...

> But then I would not be able to differentiate the behaviour according to the site. then perhaps an additional site setting is better. More costly to develop and maintain....

I propose to do only this part: > * add another preference near the existing one (to respect what the W3C standard says: the user agent allows the user to...