After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 333021 - Unsaved form confirmation not used for back/forward
Unsaved form confirmation not used for back/forward
Status: RESOLVED WONTFIX
Product: epiphany
Classification: Core
Component: Backend
3.4.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: Xan Lopez
Epiphany Maintainers
Depends on: 155603
Blocks:
 
 
Reported: 2006-03-01 17:58 UTC by Wouter Bolsterlee (uws)
Modified: 2016-02-29 20:59 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Wouter Bolsterlee (uws) 2006-03-01 17:58:46 UTC 
When closing a tab, Ephy asks for you confirmation if there are any unsubmitted form contents. This dialog should also be triggered when navigating back and forward (by button, by gesture, by using a keyboard shortcut, ...).
Comment 1 Reinout van Schouwen 2006-03-02 20:16:56 UTC 
I don't think that this s useful for Forward, when Forward means 'submit form'.
Comment 2 Jan Claeys 2006-08-15 12:53:14 UTC 
When Forward would submit a form, it should be with the original form values, not with anything new you typed, so I think it should always ask for confirmation.
Comment 3 Wouter Bolsterlee (uws) 2009-01-25 19:54:46 UTC 
Okay, what Reinout says makes sense. But what about Back?
Comment 4 Reinout van Schouwen 2009-01-26 09:20:59 UTC 
Just in the general case, "navigating away" from a page should trigger the warning. However in the current situation the warning is displayed too often when it's false alarm (the user didn't input any information at all). This should be solved first.
Comment 5 Michael Catanzaro 2016-02-28 17:03:35 UTC 
Reinout, do you still think this is a good idea?

I'm not sure I agree, because normally no data is lost on back/forward, it goes into page cache and is restored instantly, so the action is not normally destructive. But I guess that won't work on some pages, and maybe it's useful to have the warning anyway.
Comment 6 Reinout van Schouwen 2016-02-29 20:25:24 UTC 
(In reply to Michael Catanzaro from comment #5)
> Reinout, do you still think this is a good idea?
> 
> I'm not sure I agree, because normally no data is lost on back/forward, it
> goes into page cache and is restored instantly, so the action is not
> normally destructive. But I guess that won't work on some pages, and maybe
> it's useful to have the warning anyway.

When this bug was filed, I think the behavior was that form contents would be lost without warning. Now that it is restored from the cache I don't think this is as much of a problem as it used to be.