Closed
Bug 263490
Opened 20 years ago
Closed 19 years ago
lose composed mail in yahoo if click a link then click back to compose
Categories
(Toolkit :: Form Manager, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 209292
People
(Reporter: costinel, Assigned: bugs)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.7.3) Gecko/20041006 Firefox/0.10 (MOOX M3) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.7.3) Gecko/20041006 Firefox/0.10 (MOOX M3) if you are in the middle of composing a mail in a webmail page (it happened to me in yahoo mail) and you click on a link (exmaple: i clicked mail -> options on yahoo mail), then hit the back button, all the text you have struggled to compose, all those nice words you have been looking for a half an hours is gone to /dev/null and all you get is a brand new shiny empty compose page. if you are going to replace internet explorer on 'dad and mom desktop' , you definetely need to work on this issue, people! i don't f..ing care about that, i use the brilliant gmail javascript interface, but how are you going to win the battle against internet explorer if firefox 1.0 will get released with this bug? Reproducible: Always Steps to Reproduce: 1. log in to your (or someone else's) yahoo mail account at http://mail.yahoo.com/ 2. click on compose, write some text, click mail -> options 3. hit the 'back' button. you get the same page as if you clicked compose for the first time Actual Results: the text written in compose dissapeared Expected Results: the back button should have returned to the half-composed mail message
I think this is not a Firefox bug. It is a Yahoo problem, it has been like this for many years for me in IE too.
(In reply to comment #1) > I think this is not a Firefox bug. It is a Yahoo problem, it has been like this > for many years for me in IE too. ok, if you want to play with words, then if this is not a firefox bug, then it is a missing feature ? because on ie6sp1-up-to-date on xp-up-to-date this data loss does not happen.
Comment 3•20 years ago
|
||
I think I encountered a bug that could explain the problem with Yahoo. Until Firefox 1.0, any edited textarea was conserved while moving forward or backward in the page history (1.0 PRE included). With 1.0, some textarea do not remember changes anymore. To reproduce the bug, edit a page on both following wikis then move back and forth: http://en.wikipedia.org/wiki/Main_Page http://www.wikini.net/wakka.php?wiki=PagePrincipale Wikipedia textareas work as they have always worked but the Wikini ones now forget user changes. I do not understand the difference between both: they even share the same doctype XHtml 1.0 transitionnal... Sure IE's never been able to provide such great feature but I now wonder about re-installing 1.0 PRE !
This isn't a bug. It's how things that use POST work. I don't know of any user-agent that conserves the data entered into a form sent with POST, and allows it to still be there when you press the back button, whether that be IE, Firefox, Lynx, Links, Dillo, etc.
(In reply to comment #4) > This isn't a bug. It's how things that use POST work. I don't know of any > user-agent that conserves the data entered into a form sent with POST, and > allows it to still be there when you press the back button, whether that be IE, > Firefox, Lynx, Links, Dillo, etc. bug, not bug, call it however you want to. that behavior causes data loss. opera and ie takes you back where you were when you accidentally, wrongly, etc, clicked some link. get a little out of technical details and explanations and see the issue from the point of view of a simple end-user that expects that the button 'BACK' to take him/her ***back where she was before clicking that damn link***
Comment 7•19 years ago
|
||
Duping to bug 209292, which also has testcases. *** This bug has been marked as a duplicate of 209292 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Updated•16 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•