|
|
Rank: Member
Groups: Member
Joined: 1/20/2014
Posts: 20
|
Hi I'm using EO.WebBrowser in a .Net app where there are MAILTO: links. Clicking a link generates an error page saying "The scheme of the URL is unknown.". Simple HTML below that I tested to secure this was not an issue due to jQuery/html5 or something else.
Code: HTML/ASPX
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html><head>
<title>Mailto error</title>
</head>
<body>
<a href="mailto:MichaelJFox@stat.su.se">Email Michael</a>
</body>
</html>
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,071
|
Thanks for posting in the forum. This appears to be a missing feature as currently we do not handle mailto scheme. We will look into this to see if we can either handle it automatically, or provide a event so that you can handle it in your code.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,071
|
Hi, We have posted a new build that addressed this issue. The new build added a LaunchUrl event: http://www.essentialobjects.com/doc/6/eo.webbrowser.webview.launchurl.aspxInside the event, you can do anything you want to do with the new Url, or you can set e.UseOSHandler to true to let the OS handle it. Thanks!
|
|
Rank: Member
Groups: Member
Joined: 1/20/2014
Posts: 20
|
I downloaded the latest build ( 2013.0.66 ) but my app gets a warning I am using a trail version and suggest I buy it. My Key does not seem to work.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,071
|
Hi,
Your key should continue to work. However if you have a free license key, then the one WebView restrictions still apply. In that case you will see the license warning message.
Thanks!
|
|
Rank: Member
Groups: Member
Joined: 1/20/2014
Posts: 20
|
I still just have the one WebControl in my form. I removed the old refs and added the new dlls. When I got this "error" I removed the new dlls, registered the old ones and now it works. Seems like something's wrong if my old key should work.
|
|
Rank: Advanced Member
Groups: Member
Joined: 10/4/2016
Posts: 104
|
Hi,
I just wanted to follow up with you guys on this one and ask you how we could cleanly indicate we handle the event within the webView_LaunchUrl(...)?
I see the post is quite old so there may even be a better way to handle a "mailto:" now...
Because setting the UseOSHandler will do the trick however the error still pops up. So for now I have a double flitering: one to invoke the default OS handler if the webView.StatusMessage starts with "mailto:" and one in the LoadFailed handler to ignore the error based again on the webView.StatusMessage.
Thank you
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,071
|
Yes. This is still an issue. We will address this in our next build.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,071
|
Hi,
This is just to let you know that we have posted a new build that should fix this issue. In the old build mailto would trigger LoadFailed event. In the new build it would trigger LoadCompleted event thus will not trigger the error message. For an external Url, e.Task.ErrorCode would have the value of "ProceedAsLaunchUrl" (newly added ErrorCode value) inside LoadCompleted event.
Thanks!
|
|