Bug 130160 - contents of the form is lost when going back and forward, if the previous page changes
Summary: contents of the form is lost when going back and forward, if the previous pag...
Status: RESOLVED WORKSFORME
Alias: None
Product: konqueror
Classification: Applications
Component: khtml (other bugs)
Version First Reported In: 4.7.4
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Bugs
URL:
Keywords:
: 213235 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-07-02 20:27 UTC by kavol
Modified: 2023-01-22 05:05 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kavol 2006-07-02 20:27:00 UTC
Version:            (using KDE KDE 3.5.2)
Installed from:    Gentoo Packages
OS:                Linux

Hello,

when filling a form within a page, it sometimes happens that I need to look back to the previous page, so I use the "back" (er, alt+left, actually), see the information, then go forward and continue the editing, the form is filled with what I have written so far.

However, sometimes it happens that the previous page changes its contents meanwhile. Nevertheless, after going back it displays the original contents (as it was discussed in bug 14553), but after using alt+right to go forward to the form, the text is missing. In addition, the server behaves as if I have visited that page in between.

This is hard to trace, because the problem does not occur always (I was unable to catch any HTTP traffic ... maybe it is after some timeout?)
Comment 1 kavol 2006-09-10 18:42:30 UTC
still experiencing troubles in 3.5.4 - but this time I can positively confirm that Konqueror is fetching data from network when going back in history; this should not happen!
Comment 2 FiNeX 2009-11-29 22:55:19 UTC
*** Bug 213235 has been marked as a duplicate of this bug. ***
Comment 3 Dawit Alemayehu 2012-01-29 07:17:03 UTC
KDE 3 is no longer maintained. And what you are doing is really not recommended since the site can easily tell our HTTP client not to cache a given page ; so when you go back and forward without saving your committing your changes, you are doing so at your own risk.
Comment 4 kavol 2012-01-29 10:28:24 UTC
(In reply to comment #3)
> KDE 3 is no longer maintained.

please, would you be so kind to examine the report before closing?

- the version got updated to 4.3.1 ... and I can confirm the problem with 4.7.4

> And what you are doing is really not recommended
> since the site can easily tell our HTTP client not to cache a given page ;

which applies when opening the page again, not going back and forth through the history (what was viewed within the actual window, not the other history mechanism where you have a list of URLs visited and you choose one to be loaded again) - please see the abovementioned bug 14553 comment 3 in particular, which quotes the related RFC

> so when you go back and forward without saving your committing your changes,
> you are doing so at your own risk.

okay, you may call this bug a feature - but then, please change the behaviour at least to be consistent

either the contents should be lost every time, or it should be restored everytime - if it is restored in half of the cases and lost in the rest, without any chance for the user to predict the behaviour, it is a bit ... annoying, to be polite

also, when closing a window with a form filled, Konquerors warns user that the data will be lost - when going back in the history, Konqueror may just throw away the data without any warning at all
Comment 5 Andrew Crouthamel 2018-11-09 01:05:52 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Andrew Crouthamel 2018-11-20 03:56:52 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Justin Zobel 2022-12-23 00:28:30 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 8 Bug Janitor Service 2023-01-07 05:21:14 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Bug Janitor Service 2023-01-22 05:05:29 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!