From 77489c90492f496fadcd26d2b3ea06d7da2a1f28 Mon Sep 17 00:00:00 2001 From: Raymond Hill Date: Fri, 7 Aug 2015 11:27:52 -0400 Subject: [PATCH] Updated Dynamic filtering: Benefits of blocking 3rd party iframe tags (markdown) --- ...mic-filtering:-Benefits-of-blocking-3rd-party-iframe-tags.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Dynamic-filtering:-Benefits-of-blocking-3rd-party-iframe-tags.md b/Dynamic-filtering:-Benefits-of-blocking-3rd-party-iframe-tags.md index b195959..9ae113c 100644 --- a/Dynamic-filtering:-Benefits-of-blocking-3rd-party-iframe-tags.md +++ b/Dynamic-filtering:-Benefits-of-blocking-3rd-party-iframe-tags.md @@ -30,7 +30,7 @@ Ultimately, if a site breaks because it really does need legitimate 3rd-party `<


3rd-party <iframe> tags blocked by default for all sites,
except for the current site (this was for github.com) -- using a noop rule.

-But even in this case, the best advice would be to actually find from which specific hostname `iframe` tags are required, and to create a `noop` rule *only* for this hostname, rather than unblock all 3rd-party `iframe` tags on the site -- though this approach is better suited to advanced users. +But even in this case, the best advice would be to actually find from which specific hostname `iframe` tags are required, and to create a *local* `noop` rule *only* for this hostname, rather than unblock all 3rd-party `iframe` tags on the site -- though this approach is better suited to advanced users. ### Tracking protection