We have a custom web application that gets used via normal desktop browser, including IE, Chrome, and Firefox. When troubleshooting javascript type issues with this application, we can use the F12 button to open the javascript developer console.
This web application is also referenced inside of SAP GUI via the HTML Viewer.
The trouble that we have is that clicking F12 does not open the javascript developer console for us. Does anyone know how we go about opening this javascript developer console for a web application within SAP GUI HTML Viewer?
If you're using newer versions of windows, you might want to give F12Chooser.exe a try. It's the same developer console you would get from hitting F12 on IE, but it gives you the ability to choose a target to debug.
You can find the exe at C:\Windows\SysWOW64\F12\F12Chooser.exe (change SysWOW64 by System32 if you're on a 32bit machine)
Related
I have a web application which supports two click once applications. The web application works well under IE11 and both click once application launch under IE11. However I was recently trying to get my web application to operate under Chrome version 65. I installed the following ClickOnce extension under Chrome:
Meta4 ClickOnce Launcher
Now the above extension would not launch the supporting Click Once application in Chrome. The Click Once applications were developed in VS 2010.
I use php to call the Click Once application
header( 'Location: http://sanplic02.corp.mycompany.com/LaunchCatia/LaunchCatiaPWBSTART.application?licence=DP2&computername='.DisplayComputerName());
Does anybody have any ideas as to why this is so.
Any help much appreciated.
Now I eventually got my web application to work in Chrome. All of the above is correct. The extension I used was the Meta4 Click Once Launcher. The line of php code above is also correct this is how I launch the click once application supported by the web application.
So what was the underlying problem. Well essentially I was disabling my submit buttons in code. Even though the submit buttons were programmatically disabled they operated correctly under IE11 another words the submit buttons appeared enabled in IE11. However in chrome on the other hand they were disabled, hence Chrome would not execute the script that launched the click once application script. So once I removed the code to disable the submit button all went well.
The joys of cross browser compatibility.
In the Developer Tools window within the Chrome Browser, there is a "Sources" tab which in the past, I have been able to set breakpoints and step through the Javascript. I am still able to do that for a web app that I wrote. However, when I try to do the same for some another web app, the javascript file does not appear on the Sources tab. Instead, I find it on the Application tab but I do not appear to have the ability to step through the breakpoints on that tab.
How does the Application tab differ from the Sources tab and how might I be able to debug the javascript file?
So in the Chrome version of Firebug, it's lying on top of the window, thus, if the whole window has text, you will have stuff hidden behind the firebug. Is it possible to get it to be like Firefox's version, where it is part of the window screen like the developer console? The options don't seem to point to anything that indicates this option.
The Chrome extension of Firebug is based on Firebug Lite, which is a JavaScript that is injected into the website. So, there is unfortunately no way to integrate it into Chrome's UI.
Furthermore, Firebug Lite (and with that the Chrome extension) is unmaintained for several years now, so it doesn't provide the features integrated developer tools have.
Alternatives are:
Chrome DevTools
Chrome has integrated developer tools, which provide a huge amount of features for web developers.
Firefox DevTools
The Firefox developer tools allow to debug Chrome (and other browsers) remotely. This doesn't work as good as the integrated tools and provides less features, but allows you to use the same tools to debug in different browsers.
debugger.html
The debugger.html project (developed by the Firefox DevTools team) picks up the idea of Firebug Lite by providing a browser independent UI. It's based on a local web server serving a website, which allows you to debug JavaScript code in different browsers by connecting to them remotely. Unfortunately, it currently only provides a JavaScript debugger and it's unclear whether it will be extended to cover other features like an HTML inspector panel, a network panel, etc. later.
Is there any way to navigate object hierarchies in the developer console of either Chrome, Firefox, or other fairly standards compliant web browser,
using the keyboard? as you would e.g. in an IDE debugger...
Or can you easily hook in to the console from some IDE to get that convenience?
This is a question about debugging a project, not about writing the code.
I am on the final stages of developing an HTML5 web app. Fairly last minute, our client tells us it should run on IE8. Since I use the HTML5-canvas in the app, this required the addition of Google Chrome Frame. Once installed and testing, however, IE8's developer console no longer prints any data, and the HTML viewer never loads. Is this a bug? Is there a way to fix it? It will really suck if I need to debug with alerts...
From Google Chrome Frame documentation:
You can use the Web Inspector in GCF just as you would in the Google Chrome browser. To use it, right-click and choose "Inspect Element". Logging is available via the console.log method, and you can set breakpoints and inspect network activity.