|
Rank: Advanced Member Groups: Member
Joined: 12/30/2013 Posts: 68
|
On my webpage, I am trying to hide a rightclick menu. When I run it in chrome it works. When I run it in EO.webrowser, with the remote debugger attached it works. When I run it straight from the eo.webbrowser (as a user) with no debugging attached, it does not hide. It remains open. Any help would be appreciated.
var Menudiv = document.getElementById('ctl00_MainContent_pmOverdueAuditPlantMenu'); Menudiv.style.visibility = "hidden";
|
|
Rank: Administration Groups: Administration
Joined: 5/27/2007 Posts: 24,196
|
Hi, Can you try to isolate the problem into a test app and send us the test app? See here for more details: http://www.essentialobjects.com/forum/test_project.aspxThanks!
|
|
Rank: Advanced Member Groups: Member
Joined: 12/30/2013 Posts: 68
|
I may have found the issue. It appears that the timing of javascript releasing objects is different in your tool then VS Webbrowser, or chrome. This test will get more intense tomorrow, but so far it looks promising. What I did was I added an AfterReceiveHeaders method, with variable used to determine if one of the custom dll forms is run. Here is an example.
private void webView1_AfterReceiveHeaders(object sender, ResponseEventArgs e) { if (strShowDll == "frmOpenLocalFolder") { strShowDll = ""; frmOpenLocalFolder myFrm = new frmOpenLocalFolder(strShowDllParam1); try { myFrm.ShowDialog(); } finally{} strShowDllParam1 = ""; } }
Since this is the last piece before this release, I hope this works and we can get this app out and into the field soon.
Thank you for your help.
|
|
Rank: Administration Groups: Administration
Joined: 5/27/2007 Posts: 24,196
|
No problem. I am not exactly sure what you meant by "the timing of JavaScript releasing objects is different". However it is true that there can be subtle difference for timing of events between EO.WebBrowser and the actual Chrome browser. Such timing difference can be introduced by a number of factors, some of them are related to our implementation details, others are related to .NET runtime behaviors. However, there should not be any "wrong" timing sequence, in another word, even though EO.WebBrowser's timing sequence can be different than that of Google Chrome's, EO.WebBrowser's sequence should still be logical and theoretically it can occurs with Google Chrome as well. So if you observed any "wrong" sequence, please let us know.
Thanks!
|
|