This would need some input from ux, and may be a wontfix. We could make 2 prefs, one that contains the address of a special pb page, the other indicating the action taken. The latter would probably have two options, 1) take me to the special pb page (default), and 2) use my home page. The reason I think this should be done is so that extensions can provide their own start page, and so that the user should be able to skip the pb page.
Sounds worthwhile. I don't think having a pref which opens the home page is particularly useful though, because why would someone want to open their home page in private browsing mode? I mean, that is their home page, which should mean that page is not that much private, I guess...
Well, I figured since this opens a new browser session, the user may want to navigate to his home page(s). That's one of the reasons I added uiwanted :)
Created attachment 368052 [details] [diff] [review] ver. 1 Attaching a patch here for consideration, waiting on code review once there's a decision about the ui. This will bitrot once the patch in bug 481598 lands, I'll update it then (minor update, no code change).
When you're updating this patch later, could you please create a pref branch on the "browser.privatebrowsing." node?
Extensions can already load a different page by shipping their own "@mozilla.org/network/protocol/about;1?what=privatebrowsing" implementation. Do we really think that there's a need for customizability than that? BTW: Your patch doesn't handle multiple homepages (e.g. "about:|about:").
Don't know why I didn't think about this myself, but Simon has a strong point here. Now I'm leaning towards WONTFIXing this, but I'm leaving this open in order to get others' opinions as well.
Yeah, didn't think of that. In that case, this would indeed be wontfix, the extension case was really my strong point here... ->WONTFIX (unless anyone else minds)
Assignee: highmind63 → nobody
Status: ASSIGNED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.