Closed Bug 471726 Opened 17 years ago Closed 12 years ago

Create a help page to describe private browsing on mozilla.com

Categories

(www.mozilla.org :: General, defect)

Product:
www.mozilla.org
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: ehsan.akhgari, Assigned: faaborg)

References

Details

(Keywords: uiwanted)

Spinoff from bug 471627 comment 3. Original idea from Alex: [16x16 information icon] While this computer won't have a record of your browsing history, your internet service provider or employer can still track the pages you visit. _Learn More_. ------------------------------------------------- The learn more hyperlink needs to go to a page similar to the help page we were planning for larry, with additional information (and maybe a diagram) about the various entities that can collect information about you.
Support already has a document. https://support.mozilla.com/en-US/kb/Private+Browsing
(In reply to comment #2) > Support already has a document. > https://support.mozilla.com/en-US/kb/Private+Browsing The scope of this page will be different; see comment 0.
Component: Private Browsing → www.mozilla.com
Product: Firefox → Websites
QA Contact: private.browsing → www-mozilla-com
Summary: Should we have an informational private browsing related page at mozilla.com? → Create a help page to describe private browsing on mozilla.com
Version: Trunk → unspecified
The general idea is to create an informational page about private browsing, complete with diagrams and some delicious design league artwork (of the mask) similar to what we wanted to do for our identity UI. The page will talk about the various parties involved in privacy, and might have a diagram that looks something like this: [your computer] <---> [ISP] <---> [web site] We should have Johnathan look over the text, and I can try to post a first draft soon. Overall the goal of this page is to get people to understand that there is a difference between "no information is recorded on your computer" and "you can do whatever you want without any form of potential repercussion." We shouldn't underestimate a user's ability to be wildly confused about this feature. The current support document talks about what the feature does do, but this page will also incorporate a lot of information about what the feature doesn't do (which we might want to carry over into the support page as well). Also, if we decide that we would like to mention a Tor extension, the bottom of this page would probably be the right place to include a link.
Blocks: 471753
I'm confused why a help page on private browsing shouldn't be on SUMO. djst, I recall we had a bug on a help redirect for private browsing, but I don't find it right now. That had some UE that leads to it, too.
(In reply to comment #4) > > [your computer] <---> [ISP] <---> [web site] > Don't forget about adding something like [your computer] <---> [ISP] <---> Google and appropriate explanation regarding Google's "safebrowsing" thing (which is enabled by default, also in "private browsing" mode (bug 454792 is about interaction between "private-" and "safe-" browsing, BTW)). > Also, if we decide that we would like to mention a Tor extension By "Tor extension" you mean Torbutton (http://www.torproject.org/torbutton/index.html.en), right?
Alex's description of this document in comment 4 sounds like great user content. To me, it seems like a better idea to simply update https://support.mozilla.com/en-US/kb/Private+Browsing to what we want here. (In reply to comment #4) > The current support document talks about what the feature does do, > but this page will also incorporate a lot of information about what the feature > doesn't do (which we might want to carry over into the support page as well). This type of information (what the feature doesn't do) seems highly appropriate in the support article as well. What's the reason why we need a separate document again? :)
We don't need a separate document, it's just that the support document might end up containing details that aren't common to our other support documents. (For instance, describing aspects of privacy that our outside the realm of the product itself).
Let's get a link in the product to the support document so that is ready, and then we can focus on the specific content we need to include.
(In reply to comment #9) > Let's get a link in the product to the support document so that is ready, and > then we can focus on the specific content we need to include. Should I file a new bug to setup the required server redirect for the URL in comment 1?
(In reply to comment #8) > We don't need a separate document, it's just that the support document might > end up containing details that aren't common to our other support documents. > (For instance, describing aspects of privacy that our outside the realm of the > product itself). Right. This is fine and is something we're doing already. E.g. we're having documents describing how to configure third party firewalls, and a generic article about malware (http://support.mozilla.com/en-US/kb/Is+my+Firefox+problem+a+result+of+malware). Supporting Firefox is in fact in a large part about enabling people to use the web. (In reply to comment #9) > Let's get a link in the product to the support document so that is ready, and > then we can focus on the specific content we need to include. Where in the product will this be linked to? We will need a new in-product link parameter (e.g. "private-browsing"; see bug 414715 comment 26) and then setup a server redirect for it on SUMO (like bug 466125).
Depends on: 475551
(In reply to comment #11) > Where in the product will this be linked to? The about:privatebrowsing page, right after the user enters the private browsing mode. > We will need a new in-product link parameter (e.g. "private-browsing"; see bug > 414715 comment 26) and then setup a server redirect for it on SUMO (like bug > 466125). "private-browsing" seems to be fine. I filed bug 475551 for taking care of the redirect.
Any status updates here?
I believe we're waiting for Alex's first draft as mention in comment 4.
Here's what we have today: https://support.mozilla.com/en-US/kb/Private+Browsing (because of a bug, SUMO doesn't properly detect 3.1 today; manually click on 3.1 in the Actions box to customize the content for that version)
(In reply to comment #14) > I believe we're waiting for Alex's first draft as mention in comment 4. Alex, ETA please?
(In reply to comment #15) > Here's what we have today: > https://support.mozilla.com/en-US/kb/Private+Browsing (because of a bug, SUMO > doesn't properly detect 3.1 today; manually click on 3.1 in the Actions box to > customize the content for that version) For me, by default the 3.1 content gets displayed. I can tell because the other two versions have a box saying that the content is irrelevant for this version.
(In reply to comment #15) > Here's what we have today: > https://support.mozilla.com/en-US/kb/Private+Browsing (because of a bug, SUMO > doesn't properly detect 3.1 today; manually click on 3.1 in the Actions box to > customize the content for that version) David, are you referring to bug 474842, or something else?
<ot>Yes, but after clearing my SUMO cookies, the 3.1 content gets displayed again.</ot>
>Alex, ETA please? Are we blocking on getting the Web page up? I suggest we just just land this when strings open up and work on the Web page when we are in RC.
(In reply to comment #20) > Are we blocking on getting the Web page up? I suggest we just just land this > when strings open up and work on the Web page when we are in RC. The strings are already in the product; they're not being used now, of course. I think it would be better to first get the page up and then show the link in the UI, because otherwise the UI would include a non-functional link. BTW, bug 471753 is filed to handle the part related to adding the link to the UI.
This bug seems to have been forgotten. Pinging Alex about this. As I understand it, we just need the text and diagrams to add to the sumo page.
Adding the blocking flag since I imagine this would be wanted before we ship since it is a prominent new feature.
Flags: blocking-firefox3.5?
FWIW, right now this points to: http://support.mozilla.com/en-US/kb/Private+Browsing?style_mode=inproduct I think that's good enough to ship. Would be nicer to have an in-product page, sure, but don't think that blocks. It would require: - text and images (not to be generated by website team, they should come up with a first pass of text and ask Alex/Ehsan/me to do an edit pass) - altering of the redirect (presumably in .htaccess?) - l10n work
Flags: blocking-firefox3.5? → blocking-firefox3.5-
(In reply to comment #24) > I think that's good enough to ship. Would be nicer to have an in-product page, > sure, but don't think that blocks. It would require: > > - text and images (not to be generated by website team, they should come up > with a first pass of text and ask Alex/Ehsan/me to do an edit pass) > - altering of the redirect (presumably in .htaccess?) > - l10n work When the time comes, I can help with the text editing and making sure it's designed in the proper mozilla.com format for consistency's sake, etc (Alex and I have also discussed commissioning one of the mozilla.com character illustrations to represent private browsing on this page).
Not sure what's wrong with the SUMO page in terms of style? We're linking to other SUMO pages from product already, e.g. For IE Users. Would be great to get a good text review of the page though!
(In reply to comment #26) > Not sure what's wrong with the SUMO page in terms of style? We're linking to > other SUMO pages from product already, e.g. For IE Users. There's nothing wrong with that, but I think an in product page serves a different purpose (see comment 4). That page is supposed to provide the user with information about the private browsing mode, and not with a manual of how to interact with it (because we show that link in about:privatebrowsing, so chances are that the users who click on it already know how to enter/exit the private browsing mode.) The content should be an expanded version of the introduction and "What Private Browsing will not retain" section on the current SUMO page. > Would be great to get a good text review of the page though! I had already done a text review (from the technical point of view) in another bug, but I just checked the page again. All seems fine, except that on the "Start Firefox in a private browsing session" section, I'd rather mention "Never remember history" instead of the micro-managed custom pane.
Adding uiwanted to get this back on our radar. I'll try to get some text and graphics together for the page.
Keywords: uiwanted
Who this this be assigned to?
oops, I type too quickly. That should say "Who should this be assigned to?"
This is pretty old and it seems like we already have what we need. Can I close this?
Yeah, I think this was solved a long time ago in another bug...
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
This bug was not fixed. The link in about:privatebrowsing still points to the support article on how to use private browsing. The intent was create a page on www.mozilla.com that explains why your ISP can still see what you do, and use that for the link on about:privatebrowsing.
(In reply to comment #33) > This bug was not fixed. The link in about:privatebrowsing still points to the > support article on how to use private browsing. > The intent was create a page on www.mozilla.com that explains why your ISP can > still see what you do, and use that for the link on about:privatebrowsing. I don't see a link in about:privatebrowsing in 3.6. Is it 3.5 only or am I missing something? If we're still going to build this page soon, go ahead and reopen. If so, next step would be to define content and design.
It's the "Learn More" link. Screenshot: <http://ilias.ca/screenshots/pb-learnmore.png> I don't know if they still want to build the page, but the bug is not fixed.
(In reply to comment #35) > It's the "Learn More" link. > Screenshot: <http://ilias.ca/screenshots/pb-learnmore.png> > > I don't know if they still want to build the page, but the bug is not fixed. Oh, I see, you have to turn on private browsing. Thanks. Ya, resolved incomplete makes more sense, thanks. If someone wants to build this page still, please feel free to reopen. Just trying to clean up old bugs that aren't going anywhere currently.
Resolution: FIXED → INCOMPLETE
>If someone wants to build this page still, please feel free to reopen. Just >trying to clean up old bugs that aren't going anywhere currently. The discussion over in bug 587551 shows some of the issue we're encountering. Currently the page explains what private browsing does and how to use it, but it would be useful for us to broaden the discussion a bit and explain the limitations.
(In reply to comment #37) > >If someone wants to build this page still, please feel free to reopen. Just > >trying to clean up old bugs that aren't going anywhere currently. > > The discussion over in bug 587551 shows some of the issue we're encountering. > Currently the page explains what private browsing does and how to use it, but > it would be useful for us to broaden the discussion a bit and explain the > limitations. Reopening and tentatively assigning to Faaborg to come up with the page text.
Assignee: nobody → faaborg
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Component: www.mozilla.org/firefox → www.mozilla.org
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
The in-product Learn More link now point this SUMO article: https://support.mozilla.org/en-US/kb/private-browsing-browse-web-without-saving-info?redirectlocale=en-US&as=u&redirectslug=Private+Browsing&utm_source=inproduct
Status: REOPENED → RESOLVED
Closed: 15 years ago → 12 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.