Some pages of a website provide a different functionality then others.
For example, login pages often employ fingerprinting, some pages might need access to specialized APIs but others not (Geolocation, Audio, Canvas, etc.).
We should let users to apply specific behaviour per URL.
I think that URL should not consist of the query and fragment parts but this may be changed during proper design phase.
Changes in JSS, NBS, and FPD will be necessary.
The "Settings for domain" label should be converted to an interactive item (a button? checkbox?). By clicking the user will change the popup to configure JSS, NBS, FPD per-page. The domain should show the URL. We need to decide how to clearly show long URLs.
We need to provide UI there but we might reuse the UI that we currently have.
Issues like #155 and #159 deal with configuration changes to pass captchas. It would be nice to have an option to change configuration only for a limited time.
The question is how much. In one minute, the user can be fingerprinted by the page after passing captcha. Settings for several seconds might not give the user enough time to correctly tweak the configuration.
Metadata Update from @polcak: - Issue set to the milestone: None (was: NLNet evaluation)