57103 - <a onClick="self.location='foo'" href="bar"> in a frame: self.location ignored, even when href has a target

Status: RESOLVED WORKSFORME

(Core :: DOM: Core & HTML, defect, P3)

Description

[Robin Wylie]

This Code will onl change the target window, but not the self window.
It has not worked for all the buidls I've tried: m15-m18
works in netscape 4.73 and IE5
this is a snippet of the offending code:
<A HREF="../main/computers.html" onClick="window.self.location='linkcomp.html'"
 Target="main">
It is repeatable on the website
www.wyliecomputers.com
and clicking on the menu selections support or computers.

Thanks You
Robin Wylie

Comment 1

[Phil Schwartau]

Browser, not engine. Reassigning to DOM Level 0 for further triage -

Comment 2

[Jesse Ruderman]

i'm making a testcase for this bug.

Comment 3

[Jesse Ruderman]

Attachment: testcase (zipped)

Comment 4

[Jesse Ruderman]

Attachment: testcase (zipped), this time with the correct mime type

Comment 5

[Jesse Ruderman]

Updating summary, keywords.

I noticed a javascript error in navigator.js that happens when I take away the 
target (so self.location= and href= are fighting for who gets to fill the 
frame).  I don't know whether this is the same bug or a separate bug.

Comment 6

[Johnny Stenback (:jst)]

Event handling/handler problem, reassigning to Tom.

Comment 7

[Casey A. Peel]

I've ran into this problem as well and found an interesting case on some
internal company sites.

On Windows NT 4 (build 2000112704) if you _right_ click on the link to bring up
the context menu, the onClick address is honored and the href address is ignored.

If you _left_ click on the link the href address is honored and the onClick
address is ignored.

This holds true for the latest attached testcase.

Comment 8

[joki (gone)]

Hopefully just a botched logic issue.  If its a timing issue its going to be 
tough to fix.

Comment 9

[clayton]

Moving out one milestone.  Joki's plate is full.

Comment 10

[Wolfgang Schwarz]

This is fixed now. The testcase works fine in M0.9. 
It seems to have been fixed by the patch attached to bug 65777 (as rpotts
reported in bug 68955).

Comment 11

[joki (gone)]

Moving lower priority bugs out of .9.2 milestone.

Comment 12

[Blake Ross]

Doesn't look like this is getting fixed before the freeze tomorrow night.
Pushing out a milestone.  Please correct if I'm mistaken.

Comment 13

[saari (gone)]

->0.9.5

Comment 14

[joki (gone)]

Moving to 0.9.6

Comment 15

[Fabian Guisset]

Marking WORKSFORME based on Wolfgang's comments of 2001-06-16 and because it
works for bz and I in recent nightlies. Please reopen if the bug reappears.