Closed Bug 269186 Opened 20 years ago Closed 19 years ago

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

Categories

(Camino Graveyard :: General, defect, P3)

Product:
Camino Graveyard
Component:
General
Platform:
PowerPC
macOS
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME
Milestone:
Camino1.6

People

(Reporter: jon, Assigned: mikepinkerton)

References

(
URL
)

Details

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.
wow, this page has multiple <html> and <head> sections in it. oy!
Status: UNCONFIRMED → NEW
Ever confirmed: true
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.
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.
WFM now.
Status: NEW → RESOLVED
Closed: 19 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.
(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.