Open
Bug 1468323
Opened 6 years ago
Updated 2 years ago
Going Through the Tracking Protection Tour while function is disabled renders the user to be blocked at step 3/3
Categories
(Firefox :: Protections UI, defect, P5)
Firefox
Protections UI
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox-esr52 | --- | unaffected |
firefox-esr60 | --- | unaffected |
firefox60 | --- | unaffected |
firefox61 | --- | unaffected |
firefox62 | --- | affected |
People
(Reporter: bmaris, Unassigned)
Details
[Affected versions]: - Nightly 62.0a1 [Affected platforms]: - Windows 10x64 - macOS 10.13 - Ubuntu 18.04 [Steps to reproduce]: 1. Open Firefox 2. Open a new private window 3. Leave the Tracking Protection toggle to Off 4. Click on the See How it Works 5. Click Next on the first 2 tour slides [Expected result]: - The third tour slide should be displayed, and the user should be able to finish the tour after this slide. [Actual result]: - When going through the tour with the function disabled, the third tour slide will never be displayed and the user is stuck inside the tour, the site's information being displayed with no interaction option. [Regression range]: - Not a regression since its also reproducible on the build where this was introduced, Nightly 2018-06-01 [Additional notes]: - Activating the feature from the burger menu while being stuck in the tour, will simply add another option to the site information pop-up, but will still leave the user stuck. - Here is a screencast showing the issue: https://drive.google.com/file/d/1zRV0W8VSgdKi4ZTl-QDFKZzm8pqbszCN/view?usp=sharing
Comment 1•6 years ago
|
||
Another simplified method to reproduce: 1. Open Firefox; 2. Click on the Hamburger menu, turn off the Tracking Protection; 3. Acces the following link: https://www.mozilla.org/en-US/firefox/62.0a1/tracking-protection/start/?step=3
Updated•6 years ago
|
No longer blocks: 1462468
Component: Site Identity and Permission Panels → Tracking Protection
Priority: -- → P5
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•