New issue
Advanced search Search tips

Issue 889891 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
susan.boorgula@chromium.org
toyoshim@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

"target" attribute seems to be ignored for javascript: links

Reported by leose...@rambler.ru, Sep 27 
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36

Example URL:

Steps to reproduce the problem:
Click on a <a href="javascript:foo()" target="test-iframe">link</a>

What is the expected behavior?
window.frames["test-iframe"].contentWindow.foo() should be called.

What went wrong?
window.foo() called.

Does it occur on multiple sites: N/A

Is it a problem with a plugin? N/A 

Did this work before? No 

Does this work in other browsers? Yes

Chrome version: 67.0.3396.87  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version:

Comment 1 by leose...@rambler.ru, Sep 27 

Works correctly on Firefox 56.0.2

Comment 2 by vamshi.kommuri@chromium.org, Sep 27

Labels: Needs-Milestone

Comment 3 by susan.boorgula@chromium.org, Oct 16

Cc: susan.boorgula@chromium.org
Components: Blink>Loader
Labels: Triaged-ET Needs-Feedback
leoseven@ Thanks for the issue.

Tried creating and opening a Html file on Chrome with the above given code, but unable to see the expected or the actual behavior.
Hence request you to provide a sample HTML file where this issue can be reproduced, which will help in further triaging.

Thanks..

Comment 4 by toyoshim@chromium.org, Oct 16

Components: Blink>JavaScript>Parser

Comment 5 by adamk@chromium.org, Oct 17

Cc: toyoshim@chromium.org
I don't see how this is related to JS parsing; toyoshim, can you provide some background on why you added that label?

Comment 6 by toyoshim@chromium.org, Oct 17

Components: -Blink>JavaScript>Parser
Ah, sorry. I misunderstood that this was an issue on an attribute for an event handler. Let me remove the label.

Comment 7 by toyoshim@chromium.org, Oct 17

Components: UI>Browser>Navigation
Labels: -OS-Windows

Comment 8 by leose...@rambler.ru, Oct 20 

Place both files to the same directory and open testhtml.html with Chrome.
To see how it works on Firefox, open testhtml.html with Firefox.
testhtml.html
326 bytes View Download
testframe.html
161 bytes View Download
Project Member

Comment 9 by sheriffbot@chromium.org, Oct 20

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 10 by susan.boorgula@chromium.org, Nov 15

Labels: -Type-Compat Target-72 FoundIn-72 M-72 FoundIn-71 FoundIn-70 OS-Linux OS-Mac OS-Windows Type-Bug
Status: Untriaged (was: Unconfirmed)
leoseven@ Thanks for the update.

Able to reproduce the issue on Windows 10, Mac OS 10.13.6 and Ubuntu 17.10 on the latest Stable 70.0.3538.102 and the latest Canary 72.0.3610.0 as per comment #8.

This is a Non-Regression issue as this is observed from M-60 chrome builds.
Attached is the screen shot for reference.

Hence marking this as Untriaged for further updates from Dev.

Thanks..
889891-M60.png
52.5 KB View Download

Comment 11 by kouhei@google.com, Nov 21

Status: Available (was: Untriaged)
Triager here.

I checked html spec and confirmed that Chromium is not following the spec here.
https://html.spec.whatwg.org/#following-hyperlinks-2

It seems that HTMLAnchorElement correctly generate FrameLoadRequest with the target, but FrameLoader doesn't execute the script on the correct frame.
►

Sign in to add a comment