URL-related menu items don't appear if pointer is on bottom pixel of URL

Bug #234158 reported by Ralph Corderoy
2
Affects Status Importance Assigned to Milestone
Gnome Virtual Terminal Emulator
Expired
Medium
vte (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-terminal

Ubuntu 8.04, gnome-terminal 2.22.1-0ubuntu2.

Take a URL in a gnome-terminal, the pointer can be moved over it, the
URL is underlined, and mouse button 3 will bring up a context menu with
Open Link, etc.

However, if that same URL is approached from below, a pixel at a time,
and the pointer stops moving when the underline appears, and then button
3 is pressed, the context menu is lacking the URL related items. This
is despite the visual feedback of the URL being underlined.

Similarly, if the URL is approached from above, moving the pointer down
a pixel at a time until the underline appears, and then the pointer is
move back up a pixel so the underline goes, the context menu *contains*
the URL related items even though the visual feedback said it shouldn't
because of the lack of underlining.

It seems the coordinates used to determine when to underline are one-off
from the calculation of when the context menu should contain URL-related
items. There's also a one-off error left/right as opposed up/down.

I found this because I got fed up of having an underlined URL yet the
menu not containing Open Link. I was sure I hadn't moved the mouse in
the meantime, and I hadn't; I was just on the bottom row for pixels for
the URL. So it's not theoretical but bites in real life.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your report, that's more like a vte issue, re assigning accordly, thanks.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Also known upstream, you can track it here: http://bugzilla.gnome.org/show_bug.cgi?id=385695

Changed in vte:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Triaged
Changed in vte:
status: Unknown → New
Changed in vte:
status: New → Invalid
Revision history for this message
Pedro Villavicencio (pedro) wrote :

upstream bug was closed as invalid, please see the upstream url for rationale.

Changed in vte:
status: Triaged → Invalid
Revision history for this message
Ralph Corderoy (ralph-inputplus) wrote :

Actually, the bug was perfectly valid and was fixed upstream. They then decided to change the title and the issue the bug was tracking and later decided that this second issue wasn't a bug. http://bugzilla.gnome.org/show_bug.cgi?id=385695#c13

Changed in vte:
importance: Unknown → Medium
Changed in vte:
status: Invalid → New
Revision history for this message
Ralph Corderoy (ralph-inputplus) wrote :

As I stated in comment #4 above, this bug was fixed upstream. Ubuntu 10.10 seems fine; the bug's fixed.

Changed in vte:
status: New → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.