when i command click on a link, it opens a new window and still goes to the next page on the original window

RESOLVED WORKSFORME

Status

Camino Graveyard
General
P3
normal
RESOLVED WORKSFORME
14 years ago
13 years ago

People

(Reporter: Jon Stevens, Assigned: Mike Pinkerton (not reading bugmail))

Tracking

unspecified
Camino1.6
PowerPC
Mac OS X

Details

(URL)

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a5) Gecko/20041109 Camino/0.8+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a5) Gecko/20041109 Camino/0.8+

when i command click on a link in the forum to view the details of a posting, it
opens a new window (as expected) but it still goes to the next page on the
original window. It is as if the original window still receives the click.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.



Expected Results:  
i expect the new window to open with the link and the previous window to not do
anything.
(Assignee)

Comment 1

14 years ago
wow, this page has multiple <html> and <head> sections in it. oy!
Status: UNCONFIRMED → NEW
Ever confirmed: true
(Assignee)

Comment 2

14 years ago
note that even when you don't click a link (just in the table cell bg), the page
follows the link. I think they have some js that does the redirection manually.

Comment 3

14 years ago
From the page's source (in a script block):

cellHigh[ch].onclick = function(){location =
this.getElementsByTagName('a')[num].href;};

So yes, they are using JavaScript. Both the actual link href and the script are
being fired (how silly!). This is a bug on our side (AFAICT); they should really
rework their code.

Comment 4

13 years ago
WFM now.
Status: NEW → RESOLVED
Last Resolved: 13 years ago
Priority: -- → P3
Resolution: --- → WORKSFORME
Target Milestone: --- → Camino1.2
This is fixed on that page, but I think the general bug still exists (though it
might be filed somewhere else). Try command-clicking an external link in Gmail.
It'll open it in a new tab and in a new window. That's probably a different bug
though.

Comment 6

13 years ago
(In reply to comment #3)
> [...]This is a bug on our side (AFAICT)[...]

I think I meant "their" when I typed "our". It's actually pretty easy to work
around too, if one knows how to work with basic JS events.
You need to log in before you can comment on or make changes to this bug.