|
|
Rank: Advanced Member
Groups: Member
Joined: 3/13/2017
Posts: 33
|
Hi:
With the new upgrade to v 18.0.9, my WebView.UrlChanged event has stopped firing.
It worked fine in the prior version.
Any ideas?
|
|
Rank: Advanced Member
Groups: Member
Joined: 3/13/2017
Posts: 33
|
I went back to the prior version of the WebBrowser dll, and everything works again. The UrlChanged event now fires.
Is there something else that needs to be done to install the 2018 vs the 2017 editions? I updated the License in my code, and have the dll's registered.
Can't use the new version until we get this figured out...
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,221
|
Hi, We are not aware of this problem with the new build. Can you try our TabbedBrowser sample application and follow these steps: 1. Load a test page, for example, http://www.google.com; 2. Click any link in the page. The browser is redirected to another page; 3. Notice the text in the address input box changes. This change is updated by handling the WebView's UrlChanged event. Please let us know if the same steps works for you. Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 3/13/2017
Posts: 33
|
Ok - I run my program with the v 17.2.43.0 dll files, and the UrlChanged event fires each time, correctly. I replace the dll files with the 18.0.9.0 versions, and the UrlChanged event only fires once. After that, it will not fire when I change URL's in my program.
The only thing I am changing is the version of the dll files. I clean out and recompile each time. I have gone from the 17. version to the 18. version and back again. The results are consistent.
?
PS The tabbedBrowser sample works fine, by the way.
|
|
Rank: Advanced Member
Groups: Member
Joined: 3/13/2017
Posts: 33
|
The tabbedBrowser sample works fine, by the way.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,221
|
Hi, We are not sure why it works differently for you in different version. Since our sample app works fine, so we have no way of telling you what you should change to make it to work. You may want to compare the code in TabbedBrowser and your code to see if you can find out the difference. Usually as long as you find out the difference that triggered the problem, it would make sense to you. If you do find out what triggered the problem but it does not make sense to you or appear to be wrong, please try to create a test app demonstrating the problem and send the test app to us. See here for more details on how to send the test app to us: https://www.essentialobjects.com/forum/test_project.aspxOnce we have that we will be happy to investigate further. Thanks!
|
|