Update referrer-trimming after Windows rollout & clarify cookie pop-up mechanics #495
+4
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We've now released referrer header trimming on Windows, and wanted to clarify Cookie Pop-up Management function with a reference to Easylist now that we've started using their rules as well.
@alohaas, I dropped the hyphen in "open-source lists" here (and zapped the only other instance I found in the page) as the easiest path to consistency. We aren't currently using a hyphen in "open source code," which is everywhere in the doc (and involves a lot of links, so I'm a little concerned that would look busy), or a couple other instances of "open source list." However, no strong feelings about it, so I can go the other way if we want to instead add the hyphen everywhere that it technically qualifies as an adjective usage before a noun 😁 🤷♀️