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 698561 - Backspace still works as "Back"
Backspace still works as "Back"
Status: RESOLVED FIXED
Product: epiphany
Classification: Core
Component: General
git master
Other Linux
: Normal normal
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
polish
Depends on:
Blocks:
 
 
Reported: 2013-04-22 12:29 UTC by Bastien Nocera
Modified: 2014-12-11 10:37 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Bastien Nocera 2013-04-22 12:29:03 UTC 
epiphany-3.8.1-1.fc19.x86_64
webkitgtk3-2.0.1-1.fc19.x86_64

On a web page with a disable text entry (text is selectable, but not editable), I mistakenly pressed backspace, as ephy loaded the previous page.
Comment 1 Adam Dingle 2013-07-08 17:04:11 UTC 
Yes - this just bit me too.  I think it's surprising that Backspace navigates back a page - I agree with Bastien that this should not happen.
Comment 2 Claudio Saavedra 2013-08-04 09:42:50 UTC 
This is handled internally by WebKit. The WebProcess has an internal setting deciding whether backspace should be used to go backwards or even forwards (with Shift). I am not sure whether we should export the setting and flip it in Ephy or flip it internally. I will investigate.
Comment 3 William Jon McCann 2013-12-14 13:07:10 UTC 
Claudio, any news on the investigation?
Comment 4 Michael Catanzaro 2014-08-18 03:46:32 UTC 
Oh gosh, this is frustrating when it causes you to lose text.  Let's fix it.

Claudio, Carlos, do you have a preference as to whether this setting should be exposed in the API or not?  I think it probably does not matter much either way... but I doubt many browsers want this behavior.
Comment 5 Carlos Garcia Campos 2014-08-25 07:42:51 UTC 
I guess we can just disable it in WebKit.
Comment 6 Michael Catanzaro 2014-12-11 10:37:30 UTC 
This problem has been fixed for the upcoming WebKitGTK+ 2.8 release.