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 789944 - No way to copy or open-in-new-tab on touchscreen
No way to copy or open-in-new-tab on touchscreen
Status: RESOLVED NOTGNOME
Product: epiphany
Classification: Core
Component: Interface
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-11-05 21:14 UTC by kaabud-lp
Modified: 2018-01-25 15:46 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description kaabud-lp 2017-11-05 21:14:54 UTC
When using the touchscreen it is not possible to select text and copy it, or to open a link in a new tab (or window). 

I would expect that long pressing text would allow me to select and copy it. 

I would expect that long pressing a link would allow me to open in new tab/window.
Comment 1 Jan-Michael Brummer 2018-01-25 00:24:28 UTC
Shouldn't this be implemented in webkitgtk?
Comment 2 Michael Catanzaro 2018-01-25 01:39:07 UTC
At least most of the implementation would need to be in WebKit, yes. If you just make long press bring up the existing context menu, that would be an entirely WebKit-level solution. But if you want to do something special for touchscreens, e.g. equivalent to the cool GTK+ editing popup with select/cut/copy/paste options... well, if something complex like that is desired, we normally provide a default implementation in WebKit, and add API to allow applications to override it. That's where we would need Epiphany-level code to add new options.

But TBH, I have no clue what the desired user experience is, because I don't have a touchscreen. You know much better than me what the end result ought to look like. If all that's desired is a way to bring up the existing touch-unfriendly context menu, then yes that will not require any changes in Epiphany. Anyway, I'll resolve this as NOTGNOME since there's nothing to be done in Epiphany for now, at least. I know you're already working on a patch, so I trust you'll report the WebKit bug? Canned reply:

Thanks for taking the time to report this.
This issue is most likely a bug in WebKit. Please report the bug to https://bugs.webkit.org/ including a link to this bug report and noting the version of WebKitGTK+ that you have installed. When reporting the WebKit bug, be sure to include the prefix '[GTK]' in the bug summary and select the 'WebKit Gtk' component.
Comment 3 Claudio Saavedra 2018-01-25 09:04:13 UTC
I am not sure of the status of long-press popup menus in GTK+, but last thing I know this was discussed in bug #315645, which is still open.
Comment 4 Jan-Michael Brummer 2018-01-25 09:27:11 UTC
Does this really matter? Yes, a standard way officially supported by the toolkit would be nice, but for me the user matters most. If we can do it using current supported techniques than it is fine. Iff the toolkit will support a better solution we can switch as soon it is available.
Comment 5 Claudio Saavedra 2018-01-25 12:52:09 UTC
It matters in that, whichever way this is implemented in WebKitGTK+, it needs to use the infrastructure in GTK+, which is discussed in that bug.
Comment 6 Jan-Michael Brummer 2018-01-25 13:03:37 UTC
Last comment says that for the moment a longpress should be used and connected to popup-menu. Later on it needs to be changed to a more generic way.

My current patch (attached in webkit bugzilla) uses standard gtk functions to solve this issue. Is this ok?