Optionally, but by default, I think permissions should be resolved. If the user granted:
https://google.com/*
*://*/*
The latter will always include the former, so processing both is rarely useful. This is additionally shown by a Chrome issue (which I'm not sure other browsers replicate):
If webext-patterns can safely match the former with the latter, then it's easy to drop every overlapping pattern, otherwise I can just handle "all urls" as a special case.
Optionally, but by default, I think permissions should be resolved. If the user granted:
https://google.com/*
*://*/*
The latter will always include the former, so processing both is rarely useful. This is additionally shown by a Chrome issue (which I'm not sure other browsers replicate):
This module could return only
*://*/*
if found.If webext-patterns can safely match the former with the latter, then it's easy to drop every overlapping pattern, otherwise I can just handle "all urls" as a special case.