Chrome for Debugging
-
This is a qualified recommendation that you add the Chrome browser for webdialog work.
The Chrome error console caught errors that neither Firefox nor Opera found. This is good. It's confusing at first, but that's because it's far more advanced. The "Metrics" display is a boon to CSS dummies like me who could never sort out margin from padding. I would love to see a Help button.
"Qualified" refers to the bug. You get to the error console through the "Control the Current Page" icon/Developer/JavaScript console. If you change tabs, the visible tab in the browser is not the tab in the console. The tab in the console continues to show whatever you had when you launched it.
-
I would also like SU to support Chrome for web dialogs.
Chris
-
Another vote there, i especially like the ability to resize text boxes with chrome. Would make jims web console script very cool...
-
Chrome uses the webkit engine - same is Safari. I think the debugging features comes with the browser - not the render engine.
However, I do support using a platform that's supported on both platforms, instead of the current state of having two for each platform. But seeing how that probably will break backwards compatibility I'm not so sure if that will be implemented. ...or maybe, the old system could be supported, but the creating of Webdialogs would accept an extra argument where you specified the use of the new system.
-
Check out Firebug lite.
http://getfirebug.com/lite.html
It works for IE and Safari. All you have to do to debug your Webdialogs is add this line to your HTML:
<script type='text/javascript' src='http://getfirebug.com/releases/lite/1.2/firebug-lite-compressed.js'></script>
Advertisement