You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.
Currently you can open the Bravery Panel, and click on a stat. It will show a list of the URLs affected.
This task is to make it easier to troubleshoot the problems by making each of the URLs into a clickable on/off whitelist toggle. I'm thinking we can have a list of exceptions URLs for each resourceName that we keep in the siteSettings.
It's also useful for people that use noScript to incrementally add only the things they need.
Main purpose though is it'll help our QA, especially @srirambv get the info they need to report a bug that is easy for us to fix, and eventually they can make those fixes themselves to a config file and PR it.
/cc @diracdeltas, this would save us a lot of time in the long run
The text was updated successfully, but these errors were encountered:
Browsers are used by non-developers that shouldn't need to open the developer tools. And this task isn't a reporting task, it is about allowing partial blocking of a single URL at a time so that you can troubleshoot by bisection. This functionality is not even available in developer tools.
Currently you can open the Bravery Panel, and click on a stat. It will show a list of the URLs affected.
This task is to make it easier to troubleshoot the problems by making each of the URLs into a clickable on/off whitelist toggle. I'm thinking we can have a list of exceptions URLs for each resourceName that we keep in the siteSettings.
It's also useful for people that use noScript to incrementally add only the things they need.
Main purpose though is it'll help our QA, especially @srirambv get the info they need to report a bug that is easy for us to fix, and eventually they can make those fixes themselves to a config file and PR it.
/cc @diracdeltas, this would save us a lot of time in the long run
The text was updated successfully, but these errors were encountered: