The onboarding UI refers to the disable protection button as "Turn off Blocking Temporarily"
Categories
(www.mozilla.org :: Bedrock, defect)
Tracking
(Not tracked)
People
(Reporter: ehsan.akhgari, Unassigned)
Details
Attachments
(3 files)
Please see the screenshot. Test URL: https://www.mozilla.org/en-US/firefox/65.0/content-blocking/start/
| Reporter | ||
Comment 1•7 years ago
|
||
[Tracking Requested - why for this release]: Our UI says one thing, the prompt says another thing.
Comment 2•7 years ago
|
||
[Tracking Requested - why for this release]:
Comment 3•7 years ago
|
||
I'd consider this for a dot release ride-along assuming we can fix it without making string changes.
Updated•7 years ago
|
| Reporter | ||
Comment 4•7 years ago
|
||
Looks like this string is defined in bedrock:
This is good news, since it may mean that the bug could be fixed without a change to Firefox.
Moving the bug to the right component.
Comment 5•7 years ago
|
||
The URL is in the description is meant to only be opened in context of a Private Browsing window.
Attached is a screenshot of the strings displayed in Private Browsing mode.
Comment 6•7 years ago
|
||
Screenshot of strings for a normal browsing window
URL: https://www.mozilla.org/en-US/firefox/65.0/content-blocking/start/?newtab=true
Comment 7•7 years ago
|
||
Based on the above, I'm going to close this bug as invalid, since the two scenarios are intended behavior. But please feel free to re-open or let me know if you haver any questions. Thanks!
| Reporter | ||
Comment 8•7 years ago
|
||
[Tracking Requested - why for this release]:
Yes, thanks Alex. I'm almost certain that I encountered the original link out of context (e.g. on IRC or Slack) and I didn't realize we have different links for each context. Apologies for the confusion.
Description
•