Closed Bug 463477 Opened 17 years ago Closed 17 years ago

KB article: Private Browsing

Categories

(support.mozilla.org :: Knowledge Base Articles, task)

task
Not set
major

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: cilias, Assigned: bbayles)

References

()

Details

KB article the private browsing mode feature, implemented in bug 248970. I guess we could also title the article "Private Browsing mode", but the menu item is labeled "Private Browsing".
Should this article be something around the lines of this blog post (the how-to part of it, that is)? <http://ehsanakhgari.org/blog/2008-11-04/dont-leave-trace-private-browsing-firefox>
The concept of it, yes. The purpose of the article is to: * describe the feature * give one or more use cases * say what the feature does * show people how to use it * if customizable, show options
I put up a first draft for this. Notes: * It still needs screenshots, but FF3.1 isn't screenshot ready yet. * It might need revision if the UI for Private Browsing changes between FF3.1b2 and FF3.1 final. * I didn't try to add any "use cases" that pretend like this isn't an ideal feature for pr0n browsers :)
Bo: Thanks for the write-up. I fixed a number of issues in the article. (In reply to comment #3) > * It might need revision if the UI for Private Browsing changes between FF3.1b2 > and FF3.1 final. No such UI changes are planned so far for 3.1, so we're fairly safe there. > * I didn't try to add any "use cases" that pretend like this isn't an ideal > feature for pr0n browsers :) I think we will need to have use cases in that article. I'm just not sure what types of uses we would want to advocate.
- Use cases: dude....Christmas gift shopping. :-) Other than that: -- planning a surprise party -- the example in Ehsan's blog post is looking for a new job on your work computer There are more at https://wiki.mozilla.org/PrivateBrowsing#Use_Cases - A good template for the introduction would be our <http://support.mozilla.com/en-US/kb/Clearing+private+data> article. - Enabling and Disabling Private Browsing makes it seem more like a setting, than a mode. To me, it seems more like something you would "switch to" or "start". You can even call it a "mode" in the headings, so long as you don't capitalize the "m". - Use ^__Note:__ text^ for notes. - I think you should add something about "(Private Browsing)" appearing in the title bar, to indicate when in Private Browsing mode. - Try to use a numbered list for step by step instructions. This is going to be a great article. :-)
Made some edits: I added some statements based on the Clearing Private Data article. Someone else can add more use cases if necessary, but I think Mozilla's already been mocked for some of our example "extremely varied" use cases in the media. :) I really don't think we should mention searching for a new job at on your work computer, as that could really bite someone whose company keeps Internet logs upstream from client machines. Also, I put "you can be assured that your browsing history will not be easily available to people who access your computer after you use it," as it will be available to forensics experts, but maybe not your roommate. Didn't have much opportunity to use lists for step by step instructions, because there's really only one step (don't you love features like that?). Can we do screenshots yet?
I think we can split up the intro, the way the Clearing Private Data article does. Explain the concept of Private Browsing, then the next section is "What information is not recorded" (or something like that). For steps-by-step: 1. The menu. <img> 2. The prompt. <img> 3. Explain the private browsing start page. <img> Don't do screenshots yet. I'll ask for clearance after Beta 3 is released.
OK, done. Standing by for screenshots.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Moved to KB at: Wed 17 of Dec, 2008 10:58 EST We're going to have to change the "Clearing private data" link to "Clear Recent History", when that article is created.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.