It took me a while to understand that the section called "Custom Configuration" where the sub-title is TemplateS is actually a SINGLE template. To use this we have to load an already existing domain entry, save the rules to THE template, then create a new domain entry and apply the template. This isn't really a template, it's more like STORE and RECALL on a calculator, and would be much more understandable if the title was not TemplateS but just Template.
When I saw "TemplateS" I was hoping I could NAME and save templates, like MULTIPLE templates, e.g. "Enabled WebGL" or "Disable Service Workers" etc and apply these to domain rules. Even better if we could apply multiple templates to a single domain. You see the system I'm thinking about? Some way to save a template that ONLY enables all of the WebGL permissions (whereas by default they are blocked) or a template that ONLY disables Service/Web Workers (whereas by default they are allowed) and then apply multiple of these templates to each domain, modifying the base permissions...
So that's my enhancement request, to have real NAMED templates, and possibly multiple templates applied for each domain.
PS: So-called "Permitting" rules are pretty useless right now, the only rules that go there are the ones where we permit EVERYTHING. It would be better to call these "Whitelisted Domains" or something...
Good day.
It took me a while to understand that the section called "Custom Configuration" where the sub-title is TemplateS is actually a SINGLE template. To use this we have to load an already existing domain entry, save the rules to THE template, then create a new domain entry and apply the template. This isn't really a template, it's more like STORE and RECALL on a calculator, and would be much more understandable if the title was not TemplateS but just Template.
When I saw "TemplateS" I was hoping I could NAME and save templates, like MULTIPLE templates, e.g. "Enabled WebGL" or "Disable Service Workers" etc and apply these to domain rules. Even better if we could apply multiple templates to a single domain. You see the system I'm thinking about? Some way to save a template that ONLY enables all of the WebGL permissions (whereas by default they are blocked) or a template that ONLY disables Service/Web Workers (whereas by default they are allowed) and then apply multiple of these templates to each domain, modifying the base permissions...
So that's my enhancement request, to have real NAMED templates, and possibly multiple templates applied for each domain.
PS: So-called "Permitting" rules are pretty useless right now, the only rules that go there are the ones where we permit EVERYTHING. It would be better to call these "Whitelisted Domains" or something...
Thank you.