Whitelist Type Options Policy
Posted: Sun Jun 13, 2010 9:00 pm
The current EasyList and EasyPrivacy policy is that all whitelists are made as specific as possible, including always using the type options available. I feel that this is somewhat redundant if the rule already references the type through the filter itself, for example with whitelists that end with .js and also have the $script selector applied, and would therefore suggest that such unnecessary options should be removed. What do other people think about this potential change?