I have a script that runs in a browser add-on. It's using the log function of the console object that is only available when the F12 Developer Tools is loaded.
While I can disable the add-on and enable it again to see the early messages intended to be logged, I find it a bit annoying. Is there a way to load IE9 with developer tools? I'm hoping there might be an obscure argument to be passed to the application to enable that.
If this were possible, I would assume it would be mapped to a command-line options, however there doesn't appear to be any such option (though it would be a nice addition to the browser). A current list of all command line options can be found online at Windows Internet Explorer Command-Line Options.
With IE10, if you leave the Developer tool pinned to the browser window, it will be loaded the next time you open Internet Explorer after you exit.
Note that this will not work if it is unpinned.
Related
I'm new in StackOverflow and I'm a beginner in web development thank advance for your comprehension.
I have problem with SASS
it tells me well in my terminal that it compiles my code on my main.css but this shows me the result only a few times on my browser (Firefox and I cleaned his caches).
I use the terminal of VSCode (Windows Powershell) I have SASS with node.js and local server with WAMP.
I find it hard to understand my other projects I did not have this problem.
Know what I can do to fix this?
You can find my code on GitHub and a video to show you the problem.
Thank you and have a good day!
Code of my project on GitHub: https://github.com/ValentinBnmr/Semaine_Inter
Video:https://youtu.be/dV_FcwNwwcY
PS: Sorry for my poor English.
First of all, check if the value actually changes within the compiled css file. Since your Sass compiler tells you that it compiled everything successfully, it should then be changed within your css file.
It is most likely your browser's cache. Clearing it once has no effect on later reloads as seen in your video. You can set your browser (both Firefox and Chrome) to deactivate Cache while developer tools are open.
Chrome: open DevTools [Ctrl Shift i], open its settings (either hit [F1] or open via DevTools menu), under "Network" check the box at "Disable cache (while DevTools is open)
Firefox: open Web Developer toolbox [Ctrl Shift i], open its settings (same with Chrome), under "Advanced Settings" check the box at "Disable HTTP Cache (when toolbox is open)"
Whenever you load a site with those tools open (as it should be when doing stuff like this) you will never run into cache issues anymore.
I just changed from a linux/apache2.0/php4 web server to a windows/iis7/php5 web server (I only post php versions since that was a significant change).
My css is working just fine on the linux one (http://66.119.8.165/flcunderconstruction.php) but it isn't working on the windows one (http://66.119.8.236/flcunderconstruction.php).
Now, the issue only seems to be applicable to internet explorer 8 (maybe older, but I'm not testing those). Firefox and internet explorer 9 work just fine.
I think I've ruled out php issues as I created a non-php version (http://66.119.8.236/flcunderconstruction.html) and the issue persists.
I'm assuming the problem is in the css (which is quite large and throws up a lot of validation errors). But since it only occurs on the windows server and with ie8, I'm hesitant to start whacking away at the code.
Any ideas?
JJ
The broken version stops loading when it hits /include/html5.js. You only see this on IE8 because later versions handle the HTML5 stuff just fine without the polyfill.
Missing: http://66.119.8.236/include/html5.js
Present: http://66.119.8.165/include/html5.js
To test this, press F12 to open up the Developer Tools. Switch your Browser Mode to IE8. Jump over to your Network tab and press "Start Capturing". Perform a hard refresh (CTRL+F5), and watch as the files begin loading in. You'll note the 404 when it gets to the HTML5 polyfill. (Image below)
Using Fiddler2, I set up and Auto Responder to automatically add the HTML5 file from my local machine in the place of your missing file. Refreshing the request resulted in the entire site loading as expected in IE8. Put your polyfill on the other server, and you should be set.
I'm trying to use the latest Google NaCl SDK. Following the instructions at https://developers.google.com/native-client/pepper18/devguide/tutorial
I downloaded the naclsdk tool from their site, ran update, and got a pepper_18 folder.
I set NACL_SDK_ROOT to the pepper_18 folder, went in to 'examples' and ran make. Everything seemed to compile just fine.
I started Chrome, looked in about: flags and about: plugins, and verified that NaCl is enabled. I installed the SDK Examples app (from: https://developers.google.com/native-client/pepper18/sdk/examples) and that works just fine.
Then I tried to run my locally built and hosted examples, going to http://localhost: 5301. The HTML loads fine but the NaCl content does not load. In the hello world examples, it says "Status: LOADING..." forever.
I double checked the HTTP server logs and I don't see any errors there. Is there another place I should be looking for logged errors?
Check for version mismatch
In Chrome navigate to about:version and check that the major version of Chrome is at least that of the Pepper version you used to build your examples.
Check the JavaScript console in Chrome for any errors
You can find it by clicking the wrench icon in the upper right-hand corner in Chrome and selecting Tools -> JavaScript Console.
Inspect the NaCl module for further information
In the JavaScript console, you can also inspect the embed element of the NaCl module. E.g., if the embed tag has id="nacl_module" you can inspect it by typing
theModule = document.getElementById('nacl_module');
theModule.lastError;
Check Chrome's output to stdout/stderr
On Mac or Linux start Chrome from the terminal and look at the output on the console. E.g., on the Mac, you'd typically go
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --enable-nacl
On Windows, Chrome does not write to the terminal if started from a command prompt. For this reason you need to redirect stdout/stderr from Chrome by setting the environment variables NACLLOG, NACL_EXE_STDOUT, and NACL_EXE_STDERR. Point them to different files, e.g.,
NACLLOG = c:\my_project\nacl.log
NACL_EXE_STDOUT = c:\my_project\nacl_stdout.log
NACL_EXE_STDERR = c:\my_project\nacl_stderr.log
Then (re-)start Chrome (making sure these environment variables are in effect).
Connect a debugger
Instructions on using the debugging support (currently only 64-bit Windows and 64-bit Linux) are available at https://developers.google.com/native-client/pepper18/beta-docs/debugging.
Restarting Chrome means closing all windows
When developing for Native Client one often restarts Chrome. It is important to close all Chrome windows; otherwise it hasn't actually restarted.
I muddled through a few issues which I will document in case they help others:
Neglected to 'make' the examples (got a clue to make them from the asker's description).
Chrome would not let me run non-store chrome apps. Went to chrome://flags and enabled Native Client and Native Client GDB-based debugging.
The JavaScript console said the demo's nmf file under .../debug/ was missing. I changed the make config to build Debug instead of Release based on this.
Chrome console complained NativeClient: NaCl module load failed: ServiceRuntime: failed to start; NaCl's GDB debug stub requires --no-sandbox flag on Windows. See crbug…. Tried running Chrome from cmd with --no-sandbox. This results in an alert You are using an unsupported command-line flag: --nosandbox. Stability and security will suffer. The aforementioned error went away, but the examples still would not run - no UI.
Went back to chrome://flags and disabled Native Client GDB-based debugging.
Then most of the examples worked. The Google Drive demo complains Error: must be run as a packged app.
have you confirmed that you've run httpd.py from the examples folder? This script creates the localhost:5103 server that the apps can be ran from.
Also, what OS are you using?
~Main
I have currently found a way to place the currently installation of Internet Explorer into kiosk mode using asp.net and VB
System.Diagnostics.Process.Start("iexplore", "-k " & "http://www.google.co.uk")
the "-k" parameter is the command that puts the browser into kiosk mode, however, other browsers such as chrome will only put the new instance of the page into another tab and firefox just opens the browser without loading the window.
I need to know what commands to pass so that chrome and firefox will respond in the same way as IE.
Many thanks
Chrome browser can do KIOSK mode with this command.
chrome.exe --chrome-frame -kiosk "your web page".
The good thing with Chrome is that you can build apps that can use the webkit animation and they look great for a KIOSK type applications.
It sounds like you might be interested in Windows Steady State, it's discontinued and doesn't run on win 7, but if you have XP or vista, it will let you lock down the PC nice and tight. This way you can restrict the use of programs to browsers you want (if you can't lock down chrome and ff) and on a reboot, it will clear any changes to the PC, basically returning you to a clean state status
Read more here: http://en.wikipedia.org/wiki/Windows_SteadyState
Visual Studio has integrated debugging in IE, when you close IE, it stops debugging, and if you stop debugging, VS closes IE.
I want it to do the same thing with firefox/chrome! (mainly this 2, if is it possible with others, it'll be appreciated!)
Is there a way to do this?
Thanks in advance!
You need to change Visual Studio's default browser to Firefox/Chrome. To change this setting, right-click on an aspx file in Solution Explorer and select Browse With. Select the desired browser and set it as default.
What you need is to write a macro that opens up ff (or any other browser) with the debugging url.
Then you can control it and close it when the debugging ends.
but i think this task is quite hard to implement.
who mentioned here to simply set the default debug browser is not answering your question at all, b/c it will not be closed...
With Firefox established as your default browser and Firebug installed, you can debug your script in Firefox. Select Tools > Firebug > Open Firebug. The Firefox instance now shows the debugging console. To enable script debugging, click the Console tab, check the Script option, and click the "Apply settings for localhost" option.