Wevah (Nate Weaver) Reporter
	Description • 19 years ago

The summary says it all: command-clicking on a wrapping link in a table cell
selects the table cell (which it shouldn't do).

Quite noticable on Slashdot, for example.

Can someone check and see if this happens on Windows with control-click (or
whatever the key-combo is for "open in new tab")?

	Andrew Schultz
	Comment 1 • 19 years ago

worksforme with linux ctrl-click using suite trunk build 2005070105

what build are you using?

	Wevah (Nate Weaver) Reporter
	Comment 2 • 19 years ago

I'm using the Camino build from June 28th. It could be Mac, only, I suppose.

FWIW, the second or later line of the wrapped link has to be clicked; the first
line, even if it's flush left, won't cause the bug.

Command-click is both "open link in new tab/window" and "make discontinuous
selection", also, which might be confusing something, somewhere.

	Simon Fraser [no longer active]
	Comment 3 • 19 years ago

I see this every day. On the BBC site, try command-clicking one of the longer
"Also in the news" links on the RHS.

	Simon Fraser [no longer active]
	Comment 4 • 19 years ago

This seems to be Camino only. It seems to happen iff:
1. the link wraps.
2. the link is not already focussed
3. you command-click the 2nd or subsequent lines of the link

	Simon Fraser [no longer active]
	Comment 5 • 19 years ago

This reminds me of bug 255378.

	Simon Fraser [no longer active]
	Comment 6 • 19 years ago

Just as in bug 255378, removing the -moz-any-link:focus from us.css makes the
problem not occur.

	Mike Pinkerton (not reading bugmail)
	Comment 7 • 19 years ago

so does that mean it's our problem or core?

	Boris Zbarsky [:bzbarsky]
	Comment 8 • 19 years ago

Not sure, actually... I suspect core, but I could be wrong.

	Simon Fraser [no longer active]
	Comment 9 • 19 years ago

...but it doesn't happen in FF. Weird. Maybe we have different flags on the mouse click events??

	Smokey Ardisson (offline for a while; not following bugs - do not email)
	Comment 10 • 19 years ago

It looks to me like something fixed this recently on the trunk, perhaps bug 333481?

	Smokey Ardisson (offline for a while; not following bugs - do not email)
	Comment 11 • 18 years ago

Setting this to FIXED-on-trunk because I'm pretty sure the fix for bug 333481 fixed this (and none of the regression fixes for that bug have broken it).