Closed Bug 1236231 Opened 5 years ago Closed 5 years ago

[experiment] Make sure the Tracking Protection tour doorhanger is not shown when the tour starts from about:privatebrowsing

Categories

(Firefox :: General, defect, P1)

defect

Tracking

()

VERIFIED FIXED
Firefox 47
Iteration:
47.1 - Feb 8
Tracking Status
firefox46 --- affected
firefox47 --- verified

People

(Reporter: Paolo, Assigned: Paolo)

References

(Blocks 1 open bug)

Details

(Whiteboard: [fxprivacy])

Attachments

(1 file)

(In reply to Alex Gibson [:agibson] from bug 1233773 comment #4)
> I should also note a slight regression I noticed here when launching the
> tracking protection tour on step 1. Because the first use of TP might also
> be when someone launches the tour in a private window, this change results
> in a slight flicker on the first door-hanger appearing. I'm guessing because
> it is launched via the product, and then again straight after via the tour
> page loading. Everything still work ok, but we might want to add an
> exception here?

We can do either or both of these:
- Add a way for the UITour to tell Firefox that the tour has started.
- Record this when the tour button in private windows is pressed.
Flags: qe-verify+
Would it not be simpler just to not invoke the door-hanger in product if the current active tab is TP tour URL? We should try and avoid adding more things to UITour just to cover edge cases.
This is not necessarily an edge case, because it happens every time a user's first interaction with Tracking Protection (after enabling the preference) is from a private window.

Detecting the URL is not necessarily easy, as it may vary with locale or after redirects, that's why I suggested using an explicit command from the page. On the other hand, by the time the code in the page runs, it may be too late to prevent the first doorhanger from showing, so the indication would have to be provided in advance by whatever button on mozilla.org starts the tour. In the end, maybe the URL detection is better even if more complicated.
(In reply to :Paolo Amadini from comment #2)
> This is not necessarily an edge case, because it happens every time a user's
> first interaction with Tracking Protection (after enabling the preference)
> is from a private window.
> 
> Detecting the URL is not necessarily easy, as it may vary with locale or
> after redirects, that's why I suggested using an explicit command from the
> page. On the other hand, by the time the code in the page runs, it may be
> too late to prevent the first doorhanger from showing, so the indication
> would have to be provided in advance by whatever button on mozilla.org
> starts the tour. In the end, maybe the URL detection is better even if more
> complicated.

Yeah, I'm seeing the in-product triggered door-hanger appearing before the JS on the mozorg page is running. On slower network connections, this may be even more apparent. Also, the tour is not started via a button on mozorg itself, it's started by a blue CTA button on the in-product new private-browsing tab.
(In reply to Alex Gibson [:agibson] from comment #3)
> Also, the tour is not started via a button on mozorg
> itself, it's started by a blue CTA button on the in-product new
> private-browsing tab.

Don't we have a way to start the tour from the first-run page or the page that talks about privacy features anymore?
(In reply to :Paolo Amadini from comment #4)
> (In reply to Alex Gibson [:agibson] from comment #3)
> > Also, the tour is not started via a button on mozorg
> > itself, it's started by a blue CTA button on the in-product new
> > private-browsing tab.
> 
> Don't we have a way to start the tour from the first-run page or the page
> that talks about privacy features anymore?

All we currently do is prompt the user to open a new private window, for example on: https://www.mozilla.org/en-US/firefox/private-browsing/

It is up to the user to initiate the TP tour once they open a private window.
(In reply to Alex Gibson [:agibson] from comment #5)
> All we currently do is prompt the user to open a new private window, for
> example on: https://www.mozilla.org/en-US/firefox/private-browsing/

Cool! So instrumenting the tour button in product will practically cover all cases, and may be all we need to do.
(In reply to :Paolo Amadini from comment #6)
> (In reply to Alex Gibson [:agibson] from comment #5)
> > All we currently do is prompt the user to open a new private window, for
> > example on: https://www.mozilla.org/en-US/firefox/private-browsing/
> 
> Cool! So instrumenting the tour button in product will practically cover all
> cases, and may be all we need to do.

That sounds good to me - I guess there could be a gray area where someone does link to the tour directly for some reason, but hopefully this will be enough of an edge case.
Priority: -- → P2
Whiteboard: [fxprivacy][triage] → [fxprivacy]
Summary: [experiment] Make sure the automatic TP tour doorhanger is not shown when the tour starts from a different entry point → [experiment] Make sure the Tracking Protection tour doorhanger is not shown when the tour starts from about:privatebrowsing
Assignee: nobody → paolo.mozmail
Status: NEW → ASSIGNED
Iteration: --- → 46.2 - Jan 11
Priority: P2 → P1
Iteration: 46.2 - Jan 11 → 46.3 - Jan 25
Comment on attachment 8706372 [details]
MozReview Request: Bug 1236231 - Make sure the Tracking Protection tour doorhanger is not shown when the tour starts from about:privatebrowsing. r=past

https://reviewboard.mozilla.org/r/30325/#review27291

Looks good to me.
Attachment #8706372 - Flags: review?(past) → review+
Iteration: 46.3 - Jan 25 → ---
Depends on: 1233773
Priority: P1 → P2
Whiteboard: [fxprivacy] → [fxprivacy][blocked]
Assignee: paolo.mozmail → nobody
Status: ASSIGNED → NEW
Priority: P2 → P4
Whiteboard: [fxprivacy][blocked] → [fxprivacy]
https://hg.mozilla.org/mozilla-central/rev/166f314b7d4d
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 47
Assignee: nobody → paolo.mozmail
Iteration: --- → 47.1 - Feb 8
Priority: P4 → P1
QA Contact: paul.silaghi
Question:
If TP="Only in private windows" => opening cnn.com in a private window doesn't show the tour
If TP="Always" => opening cnn.com in a private window shows the tour
Is this correct?
Flags: needinfo?(paolo.mozmail)
(In reply to Paul Silaghi, QA [:pauly] from comment #12)
> Question:
> If TP="Only in private windows" => opening cnn.com in a private window
> doesn't show the tour
> If TP="Always" => opening cnn.com in a private window shows the tour
> Is this correct?

Yes, this is correct.
Flags: needinfo?(paolo.mozmail)
Verified fixed 47.0a1 (2016-02-03) Win 7, Ubuntu 14.04, OS X 10.10.5
Status: RESOLVED → VERIFIED
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.