Issue metadata
Sign in to add a comment
|
Wrong url on webview.loadabort when navigating to custom protocol
Reported by
martin.s...@gmail.com,
Jan 13 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36 Steps to reproduce the problem: 1. I have a Chrome app with webview in the root page. I try to click on <a> inside the webview to custom protocol like "mailto:name@domain.com" or "skype:0123456789". 2. The webview.loadabort event should fire and contain e.url == href from the a element. 3. The loadabort event contains "about:blank" url instead. This wrong Url is also logged into console. What is the expected behavior? The webview.loadabort event should fire and contain e.url == href from the a element. What went wrong? The loadabort event contains wrong "about:blank" url property. Did this work before? Yes Chrome 52 Does this work in other browsers? Yes Chrome version: 55.0.2883.87 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 24.0 r0 We're using NW.js framework. The loadabort method worked fine in NW.js 0.16 = Chromium 52, but right now in NW.js 0.19 = Chromium 55 it's no longer working. I've tested older builds and it's no longer working since NW.js 0.17 = Chromium 53
,
Jan 16 2017
In order to verify the positive behavior of this issue, tested it on windows 10 with chrome version #52.0.2743.0 These are the steps followed. (1) Loaded the chrome app provided in the comment #0 (2) When i clicked on the html webview app it, site not reachable error Attaching a screencast for your reference, please look into it and let us know your observations.
,
Jan 16 2017
My bad, I forgot one line in the manifest. Here's the updated sample including gif I recorded.
,
Jan 16 2017
Just a note why I reported this very specific bug in webview - we built custom lightweight browser using webview for tabs and because of this bug we're no longer able to handle any custom protocol Urls clicked inside webview. I have checked the webview documentation but found no workaround for this behavior. It's clear that the current documentation does not reflect the full behavior of webview. For instance the event loadprogress, that we use in the attached sample, is not even documented on that page: https://developer.chrome.com/apps/tags/webview
,
Jan 16 2017
,
Jan 17 2017
Just an update, the loadprogress event shows wrong url as well when "mailto:" or other custom protocol link is clicked inside the webview.
,
Jan 24 2017
Thank you for providing more feedback. Adding requester "kkaluri@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 13 2017
Cleaning up "Needs-Review" label as we are not using this label for triage. Ref bug 684919
,
Mar 13 2017
,
Mar 15 2018
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by elawrence@chromium.org
, Jan 13 2017