Thank you for your quick reply.
The if-domain only solves half the issue. For instance, if I want to whitelist
all pages under the apple.com <http://apple.com/> domain, it works with
something like this:
{
"action": {
"type": "ignore-previous-rules"
},
"trigger": {
"url-filter": ".*",
"if-domain": ["*apple.com"]
}
}
It also works with subdomains, like appleid.apple.com
<http://appleid.apple.com/>:
{
"action": {
"type": "ignore-previous-rules"
},
"trigger": {
"url-filter": ".*",
"if-domain": [“*appleid.apple.com"]
}
}
However, if I only want to whitelist a given webpage like apple.com/mac
<http://apple.com/mac>, this doesn’t work:
{
"action": {
"type": "ignore-previous-rules"
},
"trigger": {
"url-filter": "apple\\.com/mac",
"if-domain": ["*apple.com"]
}
}
This also doesn’t work since this is not a valid domain:
{
"action": {
"type": "ignore-previous-rules"
},
"trigger": {
"url-filter": ".*",
"if-domain": ["*apple.com/mac"]
}
}
Is there currently some way to only whitelist a given webpage and have all its
resources loaded?
> On Aug 13, 2015, at 11:24 PM, Alex Christensen <[email protected]> wrote:
>
> Thank you for your bug reports. Feedback like this helps improve our
> development.
>> On Aug 13, 2015, at 9:49 AM, Romain Jacquinot <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>> Hi,
>>
>> After a few days experimenting with Content Blocking in Safari, I have a few
>> questions / some feedback:
>>
>> 1) There are currently no recursive exception rules. It is therefore not
>> possible to whitelist a full website or webpage, i.e. ignoring all rules
>> regardless of where the content comes from. I've filed a bug report at
>> bugreport.apple.com <http://bugreport.apple.com/>: #22268224. Are there any
>> plans to add this feature before the release of iOS 9.0 and OS X 10.11?
> This is what if-domain and unless-domain are for. Sometimes a website needs
> a very specific rule that would break other websites, or a common rule would
> break a certain website. Try something like this:
> {"action": {"type": "ignore-previous-rules"},"trigger": {"url-filter":
> ".*","if-domain”:”*example.com <http://example.com/>”}}
>>
>> 2) Enabling content blockers from Safari Settings may be complicated for
>> some non-tech-savvy users. It would be great to be able to open Safari
>> Settings directly (or even better Content Blockers' Settings) from a
>> third-party app using URL-schemes. Bug report: #22217664
>>
>> 3) With iOS 9.0 (13A4325c), content blocking doesn’t work on iPad, only in
>> the simulator. I've filed a bug report at bugreport.apple.com
>> <http://bugreport.apple.com/>: #22217578. Is it a known bug?
>>
>> 4) There doesn’t seem to be a way to programmatically enable/disable a
>> previously-enabled content blocker without having to go through the compiler
>> again when re-enabling it. I’ve filed a bug report at bugreport.apple.com
>> <http://bugreport.apple.com/> (#22270848) with an example of use case.
>> Thanks.
>>
>> Romain
>> _______________________________________________
>> webkit-help mailing list
>> [email protected] <mailto:[email protected]>
>> https://lists.webkit.org/mailman/listinfo/webkit-help
>
_______________________________________________
webkit-help mailing list
[email protected]
https://lists.webkit.org/mailman/listinfo/webkit-help
