11 Comments

  1. Hi Chris, i’m having issues with proxy setting in youCube3. do you have any tips or pointers for getting out through a business firewall using Windows Authentication. Can you set the proxy in code the way you would with the .net 2 webbrowser?

    Reply

  2. Hi Chris, I’ve got Chrome installed and I get prompted for login details to get “out to the web”. Thing is…it doesn’t remember them and seems to prompt for every domain visited. Looks as though this might be a common problem for users in a corporate environment. I saw a Chromium post that stated that this was being worked on, with a fix expected in the next 3 months.

    Reply

  3. Hi Chris.
    I was going to try the Chromium browser wrapper, but I’ve noticed that is not working properly when the page hosts Silverlight stuffs. Try yourself, as example, to visualize the Telerik demo at http://demos.telerik.com/Silverlight/ and try the same page with Chrome: the original browser works correctly, but the wrapped version doesn’t. I guess that it could be two causes: firstly, when inside Vs2008, the output pane shows an exception (but I don’t know why and where is). Secondly, in the WebBrowser class you synchronize the visual by hard-copying the bitmap, every time the CompositionTarget ask to do it. How does that to know about the Silverlight visual management? I.e. does the Wpf ‘s CompositionTarget know anything about what inside the plugin happens? Probably the sync is missing.
    Cheers and thanks in advance for your preciuos contributions.
    Mario from Venezia.

    Reply

  4. vernarim – Awesomium exposes an “IsDirty” flag; the WebBrowser control checks that during CompositionTarget.Rendering. Additionally when it calls Awesomium’s Render method [non-asynchronously] it gets back a Rect of the updated region. That’s the only part it refreshes on the WriteableBitmap.

    Beyond that, I’ve not looked at how Awesomium/Chromium renders Silverlight and Flash. It seems to do a pretty good job, but there are certainly some Silverlight apps that don’t work, notably ones that use the WebClient stack to talk to the server (possibly because it uses the browser’s networking stack by default).

    Maybe Awesomium 1.5 (due “soon”) will improve things, or possibly porting a managed version of Awesomium (as suggested in other comment) would be the best bet… 🙂

    Reply

Leave a comment