Summary

The JShelter UX review (https://lists.nongnu.org/archive/html/js-shield/2023-01/pdfCi7H0vUsN_.pdf) identified several issues with the new level page.

Issues

[x] “Add new level” is confusing. “New level” of what?

Libor's note: This should be clarified by the redesing of the options page. The reviewer did not originally get the concept of the levels.

Patrik D.: Currently, the main settings are divided into three sections (JavaScript Shield, Network Boundary Shield, Fingerprint Detector). The "Add new level" button is located just below the preset options for "JavaScript Shield," suggesting that adding a new level will create a new JavaScript Shield setting.

[x] What are these things and which are most important?
[x] How can I find out what fingerprinting is about and why I would care?
[x] What are the effects of changing these parameters?

Patrik D.: As stated in the warning at the top of the page, when setting up JavaScript Shield, using the option to create your own level is not recommended unless you have knowledge of the subject matter. For this reason, it is not necessary to specify which settings require what level of attention or what the consequences are. If the user is interested in information about fingerprinting, they can find it on the project's homepage (https://jshelter.org/faq).

Do we want to add more pointers to help? Libor's note: I think that users adding a new level should really know what they are doing so if we scare users from adding level that seems OK.

[x] Does my description need to be like the ones shown on the green list?

cfcda9620a moved the list (green list) of unsupported APIs below the form. The point of the list is to show the user that JShelter would protect from additional threats but the browser is already protected. That might change with a browser update etc.

[x] Why are these all sliders set to off?

It is an empty level, we might as well populate the sliders with the Recommended level. To Libor other options do not make sense.

Patrik D.: A possible solution for the settings would be to adopt the parameters of the currently selected protection. However, it is much clearer to go through the options from top to bottom when setting them up, and during that, you can see which parameters have already been set.

[x] This custom-level operation apparently calls for changing some parameters, adding a name and description, and saving that, but there are no instructions for doing it.

Libor's note. If the user does not know what a level is, they should not create a level. Maybe add a warning to the beginning of the page like the one in advanced options?

Patrik D.: As mentioned, settings should only be adjusted by someone who understands this topic. The fact that there are no instructions on how to set individual parameters may discourage inexperienced users, which I consider an advantage.

OK, so let's close this one