Rank: Newbie Groups: Member
Joined: 6/19/2015 Posts: 1
|
Hi,
I am currently evaluating the EOBrowser for possible use in my commercial application/business as it ticks all the boxes for functionality that I require.
However I have one issue. I am using the EO Browser wpf component in order to render my dashboard html/css reports through this. The EO browser is working fine with any web pages I throw at it (news websites, etc.), except my current dashboard reports.
What is happening is that the scroll bars appear in the EO Browser and they are correctly sized in order to inform me that the web page containing the dashboard reports runs past the viewport area. However I cannot scroll down or across when I either click on the scroll arrows or drag the slider bar. The scroll bars are active and not disabled but I have no luck.
When I render the same dashboard report in my stand alone version of the chrome browser/firefox/etc. everything is rendered okay and they can be scrolled up/down/left/right correctly.
I wondered if there was anything you could think of that may be obvious to check for.
I currently host the wpf eobrowser control in a WPF toolwindow which the user can resize to make larger/smaller and therefore this changes correctly the scroll bar sizes in the eobrowser, but of course there is no luck with scrolling. However if I try something like the BBC web page, for example, that is fine and scrolling is okay. I use VB NET for all coding.
Thanks, Barry
|
Rank: Administration Groups: Administration
Joined: 5/27/2007 Posts: 24,229
|
Hi, Just by description we can't tell you much. You can try to download our latest build (we have just posted it today), then run the TabbedBrowser sample and see if the same problem occurs. If the same problem occurs in the TabbedBrowser, you can try to debug your code with the TabbedBrowser's built-in remote debug feature to see if you can find anything: http://www.essentialobjects.com/doc/webbrowser/advanced/remote_debug.aspxNote that you must use the latest build in order to use the remote debug feature since previous build uses an older version of Chrome engine and the remote debug protocol in that engine no longer matches that of in the current Google Chrome browser. If you still have problem debugging with the new version, you can also run another instance of the TabbedBrowser sample application as the debug client. If that still does not reveal anything, please try to isolate the problem into a test project and send us the test project. See here for more information on how to submit test project to us: http://www.essentialobjects.com/forum/test_project.aspxWe will investigate further as soon as we have the test project. Thanks!
|