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 784712 - In history, right click and choose copy location... treated differently
In history, right click and choose copy location... treated differently
Status: RESOLVED FIXED
Product: epiphany
Classification: Core
Component: History
3.22.x (obsolete)
Other Linux
: Normal minor
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-07-09 03:42 UTC by Dan Jacobson
Modified: 2017-07-09 04:14 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
history-dialog: Remove odd print statement (902 bytes, patch)
2017-07-09 03:56 UTC, Michael Catanzaro
committed Details | Review

Description Dan Jacobson 2017-07-09 03:42:32 UTC
In history, on some item right click and choose copy location.

1. In the shell that called the browser one sees a Message with the URL printed to STDERR. [ODD!]

2. The URL is not placed in the usual clipboard etc. where other copy commands place strings.
Comment 1 Michael Catanzaro 2017-07-09 03:54:18 UTC
(In reply to Dan Jacobson from comment #0)
> In history, on some item right click and choose copy location.
> 
> 1. In the shell that called the browser one sees a Message with the URL
> printed to STDERR. [ODD!]

This, I can fix.

> 2. The URL is not placed in the usual clipboard etc. where other copy
> commands place strings.

I don't understand. It works fine for me. Note that it goes to the actual cut/paste clipboard, not the primary (middle-click) selection buffer.
Comment 2 Michael Catanzaro 2017-07-09 03:56:07 UTC
The following fix has been pushed:
9b1dd36 history-dialog: Remove odd print statement
Comment 3 Michael Catanzaro 2017-07-09 03:56:10 UTC
Created attachment 355199 [details] [review]
history-dialog: Remove odd print statement

This looks like a debug leftover. We shouldn't print to stderr unless
something has gone wrong or is at least noteworthy.
Comment 4 Dan Jacobson 2017-07-09 04:14:27 UTC
(In reply to Michael Catanzaro from comment #1)
OK I'll trust about the buffer.