Location object won't show location.hostname if location.protocol contains a non typical web protocol
Reported by
breitgen...@gmail.com,
Mar 26 2016
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36 Steps to reproduce the problem: 1. Take a chromium based browser as Chrome or Vivaldi 2. Visit prepared sample page https://jsfiddle.net/q1Lafyw7/ 3. Check if there are missing values on the column 'Get Address' which display the 'hostname' attribute of the link location object What is the expected behavior? I've expected the same behavior as Microsoft Edge .. see screenshot 'edge.png' What went wrong? There is no value set for 'location.hostname' if 'location.protocol' was set to a non typical web protocol .. see screenshot 'chromium.png' Did this work before? N/A Chrome version: 49.0.2623.87 Channel: n/a OS Version: 10.0 Flash Version:
,
Mar 30 2016
Yoshino-san, you might know who could triage this better?
,
Mar 31 2016
When DoIsStandard() in url_util.cc returns false for the scheme in the URL, the URL will be parsed as-if it has a grammar like "javascript:" URLs. Forked from the reduced case in the opening comment: https://jsfiddle.net/vorjx1us/5/ At least, Chrome extracts the host part from URLs with any of the special schemes ( https://url.spec.whatwg.org/#special-scheme ) correctly. Firefox works for different set of schemes. - file: NO - sftp: YES - gopher: NO It seems both are not conforming to the URL spec https://url.spec.whatwg.org/ Even for non special schemes, when the parser sees a slash after ":", it must transition to the authority state.
,
Mar 31 2017
This issue has been available for more than 365 days, and should be re-evaluated. Please re-triage this issue. The Hotlist-Recharge-Cold label is applied for tracking purposes, and should not be removed after re-triaging the issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 25 2017
,
Apr 25 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 27 2018
This looks like a fairly high-risk change compared to the benefit.
,
Apr 27 2018
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by dtapu...@chromium.org
, Mar 28 2016