<div dir="ltr"><div>Thanks for the response.</div><div><br></div>It's a user use case. When a page doesn't work correctly, the user should be able to whitelist the page/domain.<div>The problem is that usually what was blocked is hosted on a different domain, so the other rules will still apply, and the users page still looks "broken".</div><div><br></div><div> Users don't and shouldn't have to understand that. And we shouldn't be putting them through a page inspection process.</div><div><br></div><div> But if we can do a referrer allowed, then a lot of whitelist rules will compact down into a single rule, and ease of use goes up, and the user is happy that their page at least works.</div><div><br></div><div>Also, I've been looking at the code, and playing with the json, is there a way to do combine action selectors (multiple actions per trigger or multiple selectors per action)? It doesn't appear so.</div><div><br></div><div>This is just an example, but a lot of the easylist converts to basically the same thing over and over, just with the different selectors. </div><div>I don't think that can be as efficient. I could be wrong on that, but it's also burning the 50k limit. And 11MB of text for the whole list. </div><div>I'm down to line 58,000 and the http(s) blanket is still going, at 8 lines per rule, that's 7500 rules. After compiling probably isn't that big of a deal, and internally would probably have to make it work just the same as the larger json file works anyways.</div><div><br></div><div><br></div><div>Thanks again!</div><div><br></div><p style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo"> {</p>
<p style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo"> "trigger": {</p>
<p style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo"> "url-filter": "^https?://"</p>
<p style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo"> },</p>
<p style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo"> "action": {</p>
<p style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo"> "type": "css-display-none",</p>
<p style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo"> "selector": "#A9AdsOutOfStockWidgetTop"</p>
<p style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo"> }</p>
<p style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo"> },</p>
<p style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo"> {</p>
<p style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo"> "trigger": {</p>
<p style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo"> "url-filter": "^https?://"</p>
<p style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo"> },</p>
<p style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo"> "action": {</p>
<p style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo"> "type": "css-display-none",</p>
<p style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo"> "selector": "#A9AdsServicesWidgetTop"</p>
<p style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo"> }</p>
<div><span style="font-family:Menlo;font-size:11px"> </span><span style="font-family:Menlo;font-size:11px">},</span> </div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 22, 2015 at 5:06 PM, Alex Christensen <span dir="ltr"><<a href="mailto:achristensen@apple.com" target="_blank">achristensen@apple.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
> On Sep 22, 2015, at 2:47 PM, Charles Butkus <<a href="mailto:airdamien@gmail.com">airdamien@gmail.com</a>> wrote:<br>
><br>
> Is it currently possible to write rules against http referrer?<br>
</span>It is not currently possible to do anything with the HTTP headers.<br>
<span class="">><br>
> I’m looking through the code and it doesn’t seem to be.<br>
><br>
> If a user wants to whitelist blocked content on a page hosted on a different domain, what’s the expected way of enabling this? In my head, I’d go after the referrer and whitelist based on that. if-domain and/or url-filter.<br>
</span>What exactly is your use case? Do you want to whitelist everything that you see after clicking on a link from a certain domain, no matter where that link goes? That is currently impossible with content blockers.<br>
<span class="">><br>
> Also, what’s the deal with the 50k rule limit? I’m assuming it’s for performance, but the current easylist is 46,879 entries by itself after conversion.<br>
</span>You assume correctly. It can take a lot of time and memory to compile 50k rules.<br>
<span class="">> I need to look at the data and see what I can trim down into rules with more coverage.<br>
><br>
> Thanks!<br>
</span>> _______________________________________________<br>
> webkit-help mailing list<br>
> <a href="mailto:webkit-help@lists.webkit.org">webkit-help@lists.webkit.org</a><br>
> <a href="https://lists.webkit.org/mailman/listinfo/webkit-help" rel="noreferrer" target="_blank">https://lists.webkit.org/mailman/listinfo/webkit-help</a><br>
<br>
</blockquote></div><br></div>