Open Bug 1149902 Opened 6 years ago Updated 5 years ago
The Reading List's sidebar is sometimes enabled automatically in newly opened private windows
Reproducible on: * Beta 38.0b1-build1 (20150330154247) * Aurora 39.0a2 (2015-03-31) * Nightly 40.0a1 (2015-03-31) Affected platform: Windows 7 (x64) Steps to reproduce: 1. Launch Firefox. 2. Enable the Reading List sidebar, via toolbar → bookmarks menu → Reading List → Show Reading List Sidebar. 3. Add a few pages to Reading List. 4. Open a private window, via menu → New Private Window. Expected result: The private windows opened from regular ones do not show the Reading List sidebar. Actual result: Intermittently, private windows will sometimes show the Reading List sidebar automatically if it was also enabled in the regular window. Notes: - This issue is reproducing *intermittently* so the str mentioned above are not 100% reliable. - Another issue I noticed is that the automatically opened Reading List sidebar from the private window is missing its header: (screenshot) http://i.imgur.com/BPbMagN.png. - This issue might be reproducible on other platforms as well, but I didn't yet manage to investigate it further.
I don't see a need to isolate the reader-list - there are valid reasons to choose to view specific sites in PB mode and want to select them via the sidebar. Maybe we just want a PB window to always open with the sidebar closed but able to be opened?
On Windows 8.1 32bit using Firefox 38 beta 1 (20150330154247), the Reading List sidebar is always enabled (displayed) by default in newly Private Window.
(In reply to Mark Hammond [:markh] from comment #1) > I don't see a need to isolate the reader-list - there are valid reasons to > choose to view specific sites in PB mode and want to select them via the > sidebar. Maybe we just want a PB window to always open with the sidebar > closed but able to be opened? Good suggestion, Mark. That would communicate to the user, a more private experience.
Possibly related to Bug 1168785
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.