Open
Bug 748929
Opened 13 years ago
Updated 1 year ago
Window state not restored on browser exit and restart
Categories
(Core :: Networking: Cookies, defect, P3)
Tracking
()
UNCONFIRMED
People
(Reporter: richard_collette, Unassigned)
Details
(Keywords: testcase, Whiteboard: [necko-backlog])
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 6.0; rv:12.0) Gecko/20100101 Firefox/12.0
Build ID: 20120420145725
Steps to reproduce:
Browsed to a page that sets a session cookie and the window.name which together form a "compound" browser state.
Exited the browser
Started the browser.
Actual results:
The last page is re-opened and JavaScript is re-executed.
The session cookie remains but the window.name is not set.
Expected results:
If you are going to change the definition of what session cookies are from being non-persistent to persistent, you have to be consistent and maintain the entire window state as it last existed on browser exit.
The attached JavaScript file provides an example of code that fails when the browser maintains session cookies across sessions but does not also preserve the window state.
Comment 1•11 years ago
|
||
richard, does this still reproduce for you?
Component: Untriaged → Networking: Cookies
Flags: needinfo?(richard_collette)
Keywords: testcase
Product: Firefox → Core
Reporter | ||
Comment 2•11 years ago
|
||
Flags: needinfo?(richard_collette)
Reporter | ||
Comment 3•11 years ago
|
||
Yes. This is an issue. See the newly attached test. Open browser, open file, close browser, reopen browser, restore sessions, test fails in Firefox, passes in Chrome.
No other browsers preserve session cookies across browser sessions. If an application needs this, we already have non session cookies for this purpose. If you are going to preserve one portion of the browser running state (ie. session cookies) then the entire state of the browser needs to be preserved. This may of course have security implications.
I have no idea why Mozilla wanted to make such a radical change to session cookie behavior.
Updated•9 years ago
|
Whiteboard: [necko-backlog]
Comment 4•8 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
Comment 5•8 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P1 → P3
Comment 6•5 years ago
|
||
Peterv, you have been working on session history, right? What do you think about this issue?
Flags: needinfo?(peterv)
Updated•3 years ago
|
Severity: normal → S3
Comment 7•1 year ago
|
||
I can still reproduce this issue with the attachment HTML file test. Sorry that our team doesn't have a quick thought of this problem; if it deserves a higher priority to have dom core team support, please request a new NI on me.
Flags: needinfo?(peterv)
You need to log in
before you can comment on or make changes to this bug.
Description
•