For example if we had the filter
Code: Select all
###biguglyadbox
Code: Select all
~example.com###biguglyadbox
Code: Select all
###biguglyadbox
Code: Select all
~example.com###biguglyadbox
That's correct. The screen shot is a mock up of what I am suggesting. Disabling a generic hide is not always the best solution for a user. I'm after a quick and easy way to create a hiding rule with a domain exception.Wladimir Palant wrote:Hubird, this must be a filter from a filter subscription - normally you would also have "Disable this filter on au.yahoo.com" in the menu.
If a hiding filter with a domain exception supersedes standard hiding filters (both general and for specific domain ones) then I feel having two is not a major issue (it is ultimately up to the end user to make to worry about duplicate rules of any type). The ability to create an exception rule from the context menu would also benefit those users who like to see certain ads for whatever reason (Google adsense comes to mind).Wladimir Palant wrote:The problem with that suggestion: if the filter subscription changes that filter (probably to address the very same issue) the user suddenly gets two filters, both enabled.
Code: Select all
foo.example.com#@#biguglyadbox