Closed Bug 956462 Opened 11 years ago Closed 11 years ago

GMail tab are restored to the one state before the actual state

Categories

(Firefox :: Session Restore, defect)

29 Branch
x86
Windows 7
defect
Not set
normal

Tracking

()

VERIFIED FIXED
Firefox 29
Tracking Status
firefox28 - unaffected
firefox29 + verified
firefox-esr24 - ---

People

(Reporter: alice0775, Assigned: billm)

References

Details

(Keywords: regression)

Build Identifier: http://hg.mozilla.org/mozilla-central/rev/49d2fce9a86c Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 ID:20140103030203 Reproducible: not always, but reproducible with probability of 1-3 to 1/5 Steps To Reproduce: 1. Open https://mail.google.com and Sign-in, say tab[A] --- Firefox shows "Inbox list of emails" now 2. Open any page(ex. https://developer.mozilla.org/en-US/ ) in a new tab [B] 3. Select tab [A] 4. Restart Firefox(Fire > Exit and Start Firefox) 5. Click a email to show email body --- Firefox shows "email body" as expected. 6. Switch to tab[B] 7. Switch to tab[A] and scroll email body 8. Click "Back" button at the left side of location bar in NavBar --- Firefox shows "Inbox list of emails" as expected. Session history is penultimate as expected. 9. Restart Firefox(Fire > Exit and Start Firefox) --- Observe , when bug happens, Firefox shows "email body" insted of "Inbox list of emails" Session history goes to last one. 10. Repeat from Step5 if necessary Actual Results: Firefox shows "email body" instead of "Inbox list of emails" Session history goes to last one. Expected Results: Should be "Inbox list of emails". Session history should be penultimate. Regression window(m-c) Good: http://hg.mozilla.org/mozilla-central/rev/28ccc1a2ef10 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 ID:20131217205304 Bad: http://hg.mozilla.org/mozilla-central/rev/862cb6a1cc88 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 ID:20131217210305 Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=28ccc1a2ef10&tochange=862cb6a1cc88 Regression window(m-i) Good: L:\trunk\2013\12\firefox inbound 17-Dec-2013 2216 2226 1387314179 http://hg.mozilla.org/integration/mozilla-inbound/rev/caf902c15026 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 ID:20131217130259 Bad: http://hg.mozilla.org/integration/mozilla-inbound/rev/e42976d8d656 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 ID:20131217130521 Pushlog: http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=caf902c15026&tochange=e42976d8d656 In local build, Last Good: ff4cb698555c First Bad: e42976d8d656 Triggered by: e42976d8d656 Bill McCloskey — Bug 673569 - Let each frame script have its own anonymous scope (r=smaug,Waldo,mrbkap,bsmedberg)
Assignee: nobody → wmccloskey
Confirmed. This is happening for all pinned sites.
I backed out bug 673569 for another problem, although they might have the same cause.
Can we get confirmation whether the backout in Bug #673569 has resolved this?
NI on :billm to help with comment #3
Flags: needinfo?(wmccloskey)
Could you please confirm it is fixed now, Alice? Thanks.
Flags: needinfo?(wmccloskey) → needinfo?(alice0775)
(In reply to Andrew McCreight [:mccr8] from comment #5) > Could you please confirm it is fixed now, Alice? Thanks. It seems to be fixed. (I tried 20 times, but the problem did not happen anymore). http://hg.mozilla.org/mozilla-central/rev/37516445a0b5 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 ID:20140110030650
Flags: needinfo?(alice0775)
Based on Comment 6 and Comment 2 I do not think we will need to track this since it appears to be fixed based on backout in bug 673569.
Fixed by the backout in bug 673569.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 29
Mozilla/5.0 (Windows NT 6.1; rv:29.0) Gecko/20100101 Firefox/29.0 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Build ID: 20140128031716 Tested with latest Nightly on both Windows 7 architectures and indeed, the issue is no longer reproducing due to the backout in bug 673569, as mentioned above. Marking as verified.
Status: RESOLVED → VERIFIED
Keywords: verifyme
You need to log in before you can comment on or make changes to this bug.