When I find a page that I suspect is broken by Tracking Protection, I test it by disabling Tracking Protection (using the purple shield address bar icon). If I confirm that the page was broken by Tracking Protection, I want to report the page but the "Report a problem" button is disabled when Tracking Protection is disabled for the current page. So I must re-enable Tracking Protection, click the "Report a problem" button", and then re-disable Tracking Protection for the page because it doesn't work with it enabled.
This is a frustrating workflow and I'm sure it discourages people from reporting broken pages. I have given up many times on reporting a broken page because I was too lazy to re-enable and re-disable Tracking Protection just to show the "Report a problem" button.
Perhaps the "Report a problem" button should only be shown after the user disables Tracking Protection for the current page. If the user hasn't tested the page with both Tracking Protection enabled and disabled, then how do they know that Tracking Protection caused the breakage?
When I find a page that I suspect is broken by Tracking Protection, I test it by disabling Tracking Protection (using the purple shield address bar icon). If I confirm that the page was broken by Tracking Protection, I want to report the page but the "Report a problem" button is disabled when Tracking Protection is disabled for the current page. So I must re-enable Tracking Protection, click the "Report a problem" button", and then re-disable Tracking Protection for the page because it doesn't work with it enabled.
This is a frustrating workflow and I'm sure it discourages people from reporting broken pages. I have given up many times on reporting a broken page because I was too lazy to re-enable and re-disable Tracking Protection just to show the "Report a problem" button.
Perhaps the "Report a problem" button should only be shown after the user disables Tracking Protection for the current page. If the user hasn't tested the page with both Tracking Protection enabled and disabled, then how do they know that Tracking Protection caused the breakage?