While you're at it remember that you can make the Web Browser control run the latest installed version of Internet Explorer via Registry hack or the Edge Mode Meta Header.
This means it works in WPF, WinForms, Visual Basic 6 and older, Visual FoxPro, Delphi, MFC and any other tool that might be using the ActiveX Microsoft Web Browser Control which is awesome. Note although I'm using this with my WPF application, this will work with any application that uses a Web Browser control and as long as you control the page that you are working with can set the tag to load FireBug Lite can be injected into the page. Works with any Application that uses the Web Browser Control
FIREFOX FIREBUG JAVA SCRIPT DEBUGGER CODE
I now leave that tag as a comment in the document and when I need to debug, I just un-comment the block and add my console.log code into the page. Note that you can't use the debugger or source viewer to look at code of scripts that are loaded from the file system due to security restrictions in the browser. FireBug also supports running in an external window via the startInNewWindow option, but I found that behavior spotty in the Web Browser control - the window often wouldn't open. Note that the options are passed via a hash tag that enables a couple of flags. Hooking up Firebug is as simple as adding a script to the top of the tag of an HTML page and telling it to display itself automatically. It'd be nice to have, but I can get what I need from console.log(). If you're running scripts from the file system however, you can't load those scripts, so the debugger won't work for that unfortunately. But there are plenty of things in Markdown Monster that rely on objects or methods that interact with the WPF host application, and that stuff can only run in the Web Browser control and the context of the application.įirebug Lite is a gift to provide some debugging help with this!įirebug Lite has been around forever, and it works well for the console and for DOM viewing and basic manipulation. I've been able to get by even with some fairly hairy JavaScript code in Markdown Monster (like the spell checking and auto-complete stuff), but I've been lucky in that these more complex features could run externally in a standalone browser where I could run developer tools. Yeah I know this is basic stuff, but compared to not having a Console that can display live object state with a value thrown to console.log(), this is a huge improvement over my previous string only debugging. Well, it turns out Firebug Lite can also be used inside of a Web Browser control and compared to what I've done in the past, it's freaking awesome: Running inside of the Web Browser control is actually a very similar scenario. I've used Firebug Lite way back in the days of IE 7/8 to get a minimal debugging experience in those ancient browsers when there were no debugging tools at all in them and it was a life saver. Blast from the Past: FireBug LiteĮnter Firebug Lite… this JavaScript library is basically a Console add-in for your browser that provides what developer tools provide as a standalone runnable JavaScript script that you can plug into any page. But writing out strings is a far cry from being able to see real object state in active objects.
Personally, I've been lucky: Either I've been able to debug outside of the Web Browser control loading up the page(s) in a standalone instance of Chrome or IE, or I've muddled through with string based output written to a custom HTML statusbar control that overlays the document. This means no debugger, no console, no document view - no nothin'. There's no built in debugging support in the actual Web Browser control itself. The reason: The tools are part of the Internet Explorer Shell host container, not the actual Web browser instance.
FIREFOX FIREBUG JAVA SCRIPT DEBUGGER FULL
Debugging Web Browser Controls Sucksīut debugging this code when it runs in a Web Browser Control is a royal pain in the ass: While IE has full Web Browser F12 tools, those same tools are not available inside of the Web Browser control unfortunately. My latest project, Markdown Monster, heavily uses the Web Browser control with an embedded Ace Editor instance and there's quite a bit of code that manipulates the editor via JavaScript code that's often driven from WPF and can't be debugged externally. I have a lot of WPF and WinForms applications that use the Web Browser control.
0 kommentar(er)
