"Open in new tab" doesn't respect frame src.
Reported by
natedogi...@gmail.com,
Apr 26 2018
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36 Steps to reproduce the problem: 1. go to https://jsfiddle.net/natedogith1/gxsb3gra/ 2. inspect the archive link 3. in the developer console, right click the href link 4. click "Open in new tab" What is the expected behavior? The new tab is at the appropriate location ("https://xkcd.com/archive/" in this example) What went wrong? The link was taken relative to the root website, rather than the frame's website (link opens to "https://jsfiddle.net/archive" in this example) Did this work before? N/A Chrome version: 65.0.3325.181 Channel: stable OS Version: 10.0 Flash Version:
,
May 2 2018
Seems reasonable, but I can't reproduce this in Chrome 66. Maybe it has already been fixed?
,
May 9 2018
Tested on latest Chrome Stable #66.0.3359.139, Canary #68.0.3425.0 and Chrome #60.0.3072.0 on Windows 10, Mac 10.13.3 and Debian Rodete and able to reproduce the issue. This is a non-regression issue and able to reproduce from M-60 #60.0.3072.0. Marking it as untriaged so that issue gets addressed. Note: Attached the screen cast for reference. Thanks.
,
May 14 2018
|
||
►
Sign in to add a comment |
||
Comment 1 by krajshree@chromium.org
, Apr 27 2018