Issue 5344 - Element hiding emulation exceptions

Issue 5344 - Element hiding emulation exceptions

[hub, 2017-06-21 18:54:04]

I choose to use #^# to specify an exception, to make our life simpler, instead
of the #?@# suggested in the issue. If that's a problem, I'll rework it.

[Sebastian Noack, 2017-06-22 15:57:55]

Thanks a lot for addressing this. 

On 2017/06/21 18:54:04, hub wrote:
> I choose to use #^# to specify an exception, to make our life simpler, instead
> of the #?@# suggested in the issue. If that's a problem, I'll rework it.

FWIW, I think it might be worth to add a little more complexity in favor of a
more consistent (less confusing) syntax. But that decision is up to Wladimir.

[Wladimir Palant, 2017-07-05 12:47:32]

I don't really see the point of this change. It seems that
https://issues.adblockplus.org/ticket/5344 is simply wrong stating that
emulation filters cannot be whitelisted. In fact, elemHideEmulation.js test
already makes sure that "example.com#@#:-abp-properties(foo)" will work as an
exception for "example.com#?#:-abp-properties(foo)". If anything, the issue is
that we reuse the same exception syntax for "usual" element hiding and emulation
rules. But I don't really see a problem with that.

[Sebastian Noack, 2017-07-05 12:52:22]

I'm adding Arthur to the discussion. He was the one who requested this feature.

[arthur, 2017-07-05 13:05:36]

On 2017/07/05 12:52:22, Sebastian Noack wrote:
> I'm adding Arthur to the discussion. He was the one who requested this
feature.

My bad. :( I think I didn't actually try to use the regular exception syntax.