<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I’ve filed and updated bug reports for the most important points.<div class=""><br class=""></div><div class="">1): Bug report #22383231 (only applies to OS X Content Blockers)</div><div class="">2), 3) and 5): Bug report #22268224</div><div class="">4): Bug report #22270848</div><div class="">7): Bug report #22383298</div><div class=""><br class=""></div><div class="">Regarding point 7):</div><div class="">- It appears to be a bigger issue than I thought. I haven’t found any workaround for generic rules.</div><div class="">- The additional load-type should not be based on the security origin but on a more naive implementation: subdomains should be considered as first-party.</div><div class="">- The protocol should also be ignored for the additional load-type. </div><div class=""><br class=""></div><div class="">Is there any workaround for this point I’m not aware of?</div><div class=""><br class=""></div><div class="">Thanks.</div><div class=""><br class=""></div><div class="">Romain</div><div class=""><br class=""><div class=""><div><blockquote type="cite" class=""><div class="">On Aug 20, 2015, at 2:17 AM, Romain Jacquinot <<a href="mailto:rjacquinot@me.com" class="">rjacquinot@me.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi,<div class=""><br class=""></div><div class="">Based on our previous discussions and some additional limitations I encountered recently, here is a summary of my feedback regarding content blocking in Safari:</div><div class=""><br class=""></div><div class=""><b class="">Much needed</b><b class=""> (no adequate workarounds </b><b class="">currently </b><b class="">available):</b></div><div class=""><br class=""></div><div class="">1) A resource-type for plugin-initiated requests.</div><div class="">2) Ability to add exception rules for a specific page (not just the domain) that applies for all of its content and frames. Same as point 5 below.</div><div class="">3) Ability to add exception rules for a specific page (not just the domain) loaded within another page (frame) that applies for all of its content and frames. I thought "if-domain" and "unless-domain” alone would be sufficient for my use cases, but unfortunately they aren’t.</div><div class=""><div class=""><div class=""><br class=""></div><div class=""><b class="">Desired improvements (workarounds exist but result in a bad user experience):</b></div><div class=""><br class=""></div><div class="">4) Ability to programmatically enable/disable a previously-manually-enabled content blocker without having to go through the compiler every time.</div><div class="">5) Ability to whitelist/blacklist a full webpage or website for a content blocker without having to go through the compiler for all the rules, for instance by using a separate JSON file as discussed here <a href="https://lists.webkit.org/pipermail/webkit-help/2015-August/003954.html" class="">https://lists.webkit.org/pipermail/webkit-help/2015-August/003954.html</a></div><div class=""><br class=""></div><div class=""><b class="">Welcomed improvements (workarounds exist but are not always elegant):</b></div><div class=""><br class=""></div><div class="">6) A resource-type for plugins (object) like Flash, Java, etc.</div><div class="">7) An additional load-type: the current implementation considers as third-party both content from completely different domains and content from different subdomains but with the same domain. There should be a 3rd available load-type where all subdomains are considered as first-party.</div><div class="">8) Wider support of regular expressions: support for (abc|def), {n}</div><div class=""><br class=""></div><div class="">Thanks.</div></div><div class=""><br class=""></div></div><div class="">Romain</div></div>_______________________________________________<br class="">webkit-help mailing list<br class=""><a href="mailto:webkit-help@lists.webkit.org" class="">webkit-help@lists.webkit.org</a><br class="">https://lists.webkit.org/mailman/listinfo/webkit-help<br class=""></div></blockquote></div><br class=""></div></div></body></html>