Would it be useful to include a button in about:privatebrowsing to leave this mode, in addition to the current text which explains how to do it? I'm thinking that users are more likely to read the text of the button than they are to read the text on the page... Alex: just an idea, feel free to WONTFIX if you don't agree! :-)

I'm not sure we expect users to keep that tab open or navigated to about:privatebrowsing, and adding the button might give them an incentive to keep the tab around, if they assume that this is the only way to exit. Also, with two existing ways to exit the mode, a third way kind of feels like too much.

(In reply to comment #1) > I'm not sure we expect users to keep that tab open or navigated to > about:privatebrowsing, and adding the button might give them an incentive to > keep the tab around, if they assume that this is the only way to exit. Also, > with two existing ways to exit the mode, a third way kind of feels like too > much. Alex, I know what you mean about keeping the tab around. I guess I was optimizing for the first encounter use case. But something puzzled me: you mentioned two ways to exit the mode. We only have one: unchecking the menu item, right?

>But something puzzled me: you mentioned two ways to exit the mode. We only >have one: unchecking the menu item, right? Or closing all of the private browsing windows

(In reply to comment #3) > >But something puzzled me: you mentioned two ways to exit the mode. We only > >have one: unchecking the menu item, right? > > Or closing all of the private browsing windows Oh, as discussed in bug 411929 we decided not to do that. Is that OK with you?

>Oh, as discussed in bug 411929 we decided not to do that. Is that OK with you? Ok, I'll comment over there.

So I guess this is WONTFIX then, right? :-)

Yeah, I think we want this message to be just something that starts the mode off, not something the user keeps around the entire time.

Mass moving of all Firefox::General private browsing bugs to Firefox::Private Browsing.

Minusing for in litmus as this bug has been won't fixed.