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 360488 - An invalid url should not delete what is in the location entry
An invalid url should not delete what is in the location entry
Status: RESOLVED DUPLICATE of bug 360465
Product: epiphany
Classification: Core
Component: Interface
2.16.x
Other Linux
: Normal normal
: ---
Assigned To: Epiphany Maintainers
Marco Pesenti Gritti
Depends on:
Blocks:
 
 
Reported: 2006-10-07 20:17 UTC by Jon Dufresne
Modified: 2006-10-08 16:53 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jon Dufresne 2006-10-07 20:17:58 UTC
Use case:

1. Hit ctrl+t to go to a new tab.
2. Hit ctrl+L to get to the location entry.
3. Type 'search term' and then hit enter.
4. A dialog will pop up that says "The URL is not valid and cannot be loaded."
5. As this happens that search term is deleted from the location entry (or if a different page was loaded the URL of that other page returns).
6. I want to go back to the location entry but use my search term with a smart bookmark but it has already been deleted.

Epiphany appears to put the previous URL back in the location entry if the typed URL is invalid. I consider this bad behavior as the user is probably still interested in the URL he/she previous typed even if it was invalid. Strangely enough, if I go to a different tab and then back to the tab I typed 'search term' in the search term is back. This coming back feature is there whether or not the page was originally blank.

I propose the location entry not be immediately deleted unless the text entered was successful. The user may press 'Esc' if he/she wishes to bring the old URL back.
Comment 1 Diego Escalante Urrelo (not reading bugmail) 2006-10-08 16:53:25 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 360465 ***