|
|
Rank: Advanced Member
Groups: Member
Joined: 6/20/2016
Posts: 32
|
I believe I have found a bug with the latest 2018 version of EO webbrowser. When I navigate around on Pinterest.com, the BeforeNavigate event does not always fire. I ran some tests and confirmed this is not an issue with the previous version I used (17.2.92).
This is time-critical for me, I cannot wait for an update... would you mind providing me with a download location for one of the earlier 2018 versions? 18.0.9 should be fine.
Thank you for your help.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,071
|
Hi,
Please see your private message for the download location of the 18.0.9 build.
For performance reason, there is a very short time out value in the browser engine on BeforeNavigate event. So if your application is busy and could not handle BeforeNavigate event fast enough, it will be skipped. This is the #1 reason when BeforeNavigate event is not fired. So that might be something you want to look into.
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 6/20/2016
Posts: 32
|
Thank you!
Sadly the problem persists with that version as well. FYI, I have confirmed this with your tabbedbrowser sample app. Browsing around certain sections of the Pinterest website does not trigger a change to the URL in the address bar.
I'll have to hope a future version fixes this, in the meantime I can code a workaround in my software.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,071
|
If it doesn't trigger Url change in the address bar, then it's probably because indeed a navigation never has happened. For better user experience, many modern web pages do not navigate --- it simply uses AJAX to load new contents from the server and update the UI with the new contents received from the server. In this case no navigation has actually taken place. You can easily confirm whether this is the case with a network monitor application such as Fiddler.
|
|
Rank: Advanced Member
Groups: Member
Joined: 6/20/2016
Posts: 32
|
I completely understand that, however I've done the testing (in the past hour) and it works 100% when using the tabbedbrowser sample on version 17.2.92. And regular Chrome too. Therefore it has to be an issue with the current version?
Unfortunately there are other issues with that older version that prevents me from going back.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,071
|
These are all different versions of the browser engine and they CAN behave in slightly different ways. More over the page can have code that detects browser version and acts differently. So just because one work the way you wanted does not mean others must work the same way. The first thing you should check is to to use a traffic monitor to verify if navigation has indeed taken place. If navigation has indeed taken place but BeforeNavigate is not fired, then you can provide detailed step by step producing information and we will investigate further.
For your information, EO.WebBrowser 2017 is based on Chromium V54. EO.WebBrowser 2018 is based on Chromium V62. The current version of the regular Google Chrome browser can be either V63 or V64.
|
|
Rank: Advanced Member
Groups: Member
Joined: 6/20/2016
Posts: 32
|
Thanks, I appreciate your detailed response. I'm having some trouble with Fiddler, but I'll try an alternative asap.
I ran another quick test that I'd appreciate your comment on... after browsing around in the tabbedbrowser sample and noticing the events not firing (and thus the URL in the nav bar not changing), I opened the console and entered window.location.href... then it does actually give the correct URL!
For example if I navigate to Pinterest.com, and then navigate to the settings page, the URL at the top stays at "https://pinterest.com", but window.location.href indicates "https://pinterest.com/settings".
Correct me if I'm wrong, but shouldn't the URL in the nav bar above the browser reflect window.location.href?
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,071
|
Yes and no. The Nav bar should change in this case and this is indeed an issue on our side that we should be able to resolve in the near future. However window.location.href changes does NOT equal to a navigation. One situation this can happen is when the browser history has been manipulated through history API (look for "Example of replaceState() method"): https://developer.mozilla.org/en-US/docs/Web/API/History_APIMost likely this is something Pinterest is doing. When the Url is changed this way no navigation has occurred and no BeforeNavigate event will be fired.
|
|
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 Url not updating problem. You can download the new build from our download page. Please take a look and let us know how it goes.
Thanks!
|
|