(In reply to Oana Botisan, Desktop Release QA from comment #2) > Created attachment 9107797 [details] > numbers not arabic.gif > > I tried with the same steps and with the prefs from comment 1 on Windows 10 x64 using Firefox 71.0b8. The doorhanger wasn't triggered. > Only when I changed the pref: "browser.contentblocking.cfr-milestone.milestones" from "[1, 5000, 10000, 25000, 50000, 100000, 500000]" to "[20, 5000, 10000, 25000, 50000, 100000, 500000]" on the same profile, the doorhanger was triggered. > I would like to mention that the numbers in about:protections and in about:config (when trying to change the value of any pref) are not Arabic. I think it might be a translation error or something related to that. This might be the reason the issue is reproducing. Please look at the attached gif. I believe this is the same issue as Bug 1593258. You need to navigate to 4+ pages first, then reset "browser.contentblocking.cfr-milestone.milestone-achieved" to "0". This will be fixed in the patch I posted in that bug.
Bug 1594662 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Oana Botisan, Desktop Release QA from comment #2) > I tried with the same steps and with the prefs from comment 1 on Windows 10 x64 using Firefox 71.0b8. The doorhanger wasn't triggered. > Only when I changed the pref: "browser.contentblocking.cfr-milestone.milestones" from "[1, 5000, 10000, 25000, 50000, 100000, 500000]" to "[20, 5000, 10000, 25000, 50000, 100000, 500000]" on the same profile, the doorhanger was triggered. > I would like to mention that the numbers in about:protections and in about:config (when trying to change the value of any pref) are not Arabic. I think it might be a translation error or something related to that. This might be the reason the issue is reproducing. Please look at the attached gif. I believe this is the same issue as Bug 1593258. You need to navigate to 4+ pages first, then reset "browser.contentblocking.cfr-milestone.milestone-achieved" to "0". This will be fixed in the patch I posted in that bug.
(In reply to Oana Botisan, Desktop Release QA from comment #2) > Only when I changed the pref: "browser.contentblocking.cfr-milestone.milestones" from "[1, 5000, 10000, 25000, 50000, 100000, 500000]" to "[20, 5000, 10000, 25000, 50000, 100000, 500000]" on the same profile, the doorhanger was triggered. I believe this is the same issue as Bug 1593258. You need to navigate to 4+ pages first, then reset "browser.contentblocking.cfr-milestone.milestone-achieved" to "0". This will be fixed in the patch I posted in that bug.