I am using Firefox 28.0 on Mac OS 10.6.8. Sometimes during web development, probably after my application crashes, Firefox suddenly disables Javascript in one particular tab. So my application would be all weird and not work until I restart Firefox. The script panel would say that the page has no scripts, and if I open another page with Javascript in the same tab, it would not work either.
Is it some kind of safety feature? Is it documented anywhere? Note that I also have Firebug installed, and I managed to crash Firefox by profiling my app in Firebug on more than one occasion.
I checked about.config; javascript.enabled is set to true.
Related
I'm currently working on an Angular application (7.2.10) and on the latest version of iOS available on my device (12.4.1) we have hit an issue that I can't seem to figure out. The issue only occurs on Chrome on iOS, I am unable to replicate this issue on any other browser on the affected devices. The iPad air (1st gen) I am running against is using Chrome version 77.0.3865.93. It was first reported by a colleague using an iPad Pro, and we have has a couple of clients call in saying it's not working on their iPhones.
If we load the entry point to our web application (https://ams.invenias.com) the screen is completely blank. Nothing loads, and the spinner stops immediately.
I've tried a few avenues to try and get to the root of the problem, but I am yet to get anywhere. I have...
Using ios-webview-app to run iOS simulator within safari on a mac. This just resulted in the website loading as normal, so something wasn't being simulated correctly.
ios-webkit-debug-proxy to attempt to get developer tools in chrome for iOS. This ended up not working at all, either I was unable to get it running or our particular network setup meant it would never work.
Using weinre to get some sort of developer tools to read network activity/logs. I wasn't able to get this running initially, however after a bit of tinkering I was able to use this alongside Browserstack to get developer tools. Unfortunately, nothing in the logs or DOM was erroring or showed any reason as to why it might not be starting correctly.
After connecting via number 3, I was able to find out that angular itself is not bootstrapping, and no javascript is being executed on the page (from within the transpiled code, javascript included in other .js files, or within index.html executes correctly.) I'm now on day 3 with this issue, and no end in sight.
Oddly enough, if we use the 'Request Desktop Site' feature within the browser, the site loads perfectly.
Thanks,
Cameron
Long story short I'm looking to create a Chrome extension that will run within a site that only wants to run Internet Explorer (Oracle EBS). So far my only option has been to run IE Tab, which works fine when visiting the site. My new extension right now just runs alert("foo"); once a page loads and that works fine as well.
The new extension does not run in IE Tab though. Using IE Tab changes the URL to:
chrome-extension://IE_Tab's_extension_ID/nhc.htm#url=site_url
and nothing happens. Is there a way to run the extension within the IE tab extension? If anyone has an alternative idea as well I'm open to suggestions.
FYI, I ended up not doing much with IE tab or chrome. Placing a script into it's nhc.htm worked but ended up being slower and clunkier than my solution.
Instead I resorted to just using the old version of Chromium 44 (make sure it's Chromium, not chrome) and enabling the NPAPI in the chrome://flags/#enable-npapi. It's outdated tech, but really it's just there to occasionally run specific Java apps along with the new chrome extension, not replace their current browser.
I hava situation where some javascript a web page works fine in Safari and Chrome, but fails in IE11. Unfortunately due to issues with confidentiality I cannot put the javascript up here.
In IE11 the web page's java script fails to operate correctly. By that I mean some of the javascript works and some doesn't. With no errors displayed or any other indication of whats wrong.
If I try to debug the page using IE's developers tools, all the javascript works perfectly without any errors or issues.
Searching on the net I found many people with the same IE problem - fails normally, works when debugging. The main issues they talk about is the console.log(...) statement. I checked my javascript and don't have any console.log(...) statements.
I then saw a stackoverflow thread where adding a cache:false to the $.ajax({... calls solved the issue. I added the same flag but the problem still persists.
Are there any other bugs I've not found?
The web page is using jQuery to handle most of it's manipulation of the DOM with a single $.ajax... call and a series of $.get(... calls polling the server.
How to debug your web pages.....IE11 tips.
All modern web browsers suppress scripting error messages and warnings by default. (In the early days web browsers would halt page loading/rendering and display a script error message with an alert statement)... this gives the best user experience who isn't concerned with the internal workings of web site code.
So, scripting errors will only BREAK execution if:
1. The browser debug tool is opened. and
2. The developer tools' Debug tab setting for Break on Exceptions has been turned on.
So to debug your web pages.
1. navigate to about:blank to start a testing cycle.....press f11 to display the dev tool, select "Break on all exceptions" from the dropdown (looks like a stop sign). Pin the dev tool to the bottom of the browser.
2. Return to the browser address bar and navigate to your test site (typed address of paste and go)...
The dev tool will now break on ALL exceptions and you will list them in the console tab.
IE has built-in content blocking and has ActiveX filtering (ad blocking) which can affect outcomes. You need to configure Internet Options so that the IE dev tool console will record any blocked content or security (XSS) errors.
Tools>Internet Options>Advanced tab, check "Always record developer console messages".
Also on the Emulation tab of the IE dev tool you will find the Emulation Mode (aka documentMode) that IE is using, and how it was established eg. x-ua meta, Enterprise site mode list, user Compatibility View list, etc
If you are developing an internal company website, the emulation mode used by IE may be for an earlier version of IE.. (IE8 on XP).. you should include this information with your questions.
You should also include the IE security zone that your site has been mapped to.. File>Properties menu in IE.... eg. Intranet zone as this can have different security and blocked content outcomes.
finally, the first step in troubleshooting web browser issues is to test in noAddons mode (for IE, winkey+r>iexplore.exe -extoff ). IE has built-in form-fillers and popup blockers... third-party addons can affect the outcomes expected.
I am creating a purely browser based app - HTML and JavaScript.
I do not have an Android IDE installed (nor one for iOS) - and would prefer not to have to install one and perform remote debugging.
Developing on my PC, I use the Chrome browser and the developer tools to view the JavaScript console in order to debug.
How can I do that on an Android tablet (or, later, iOS)? I prefer a purely browser based solution, but could accept an Android/iOS based app.
Try https://github.com/liriliri/eruda
All you need to do is add this snippet on top of the page:
<script src="https://cdn.jsdelivr.net/npm/eruda"></script>
<script>eruda.init();</script>
And you get an interactive set of developer tools similar to those in Chrome and Firefox. Here's a screenshot:
Just released for iOS, Chrome 73 now supports the option to see console.log.
If you’re a website developer, you can now view JavaScript console
messages. Navigate to chrome://inspect to enable, then perform desired
actions in another tab. Switch back to the same chrome://inspect tab
to view any printed JavaScript console logs.
see here in "What's New" section or in "version history" 73.x version.
For Android you can use remote debugging through chrome as described here
I'll summarize/rewrite the steps (for browser based debugging) here in case the link ever goes down.
Requirements:
For browser tabs: Android 4.0+ and Chrome for Android
A USB cable to plug in your Android device
Chrome 32 or later installed on your development machine
Set up:
Enable USB debugging on your device.
Navigate to chrome://inspect/#devices on your desktop Chrome browser. (Alternatively, to get to the same screen, you can select Chrome menu > Tools > Inspect Devices)
After connecting, you may see an alert on the device requesting permission for USB debugging from your computer. Tap OK
Chrome should now display the connected device
Open up chrome on your Android device and navigate to the page you want to debug/inspect. The page should show up on your desktop browser and you should be able to inspect it.
If for some reason you have an older version of chrome and cannot upgrade. There is a plugin that you can install to accomplish the same thing.
I was searching for a while for something like this. Firebug Lite used to be an option but has been abandoned. Before discovering eruda (as mentioned elsewhere in this thread), I developed my own open source console. It's pretty light on features, but it does the main things - capture JS errors, and allow you to run commands to inspect variables and object on your page.
Here's a demo:
It's activated by just placing this script tag on your page:
<script src="https://cdn.jsdelivr.net/gh/SimonEast/MiniConsoleJS#main/console.js"></script>
Open source, GPL licence. Available at: https://github.com/SimonEast/MiniConsoleJS/
I used to be able to debug javascript from webstorm with no problem at all.
Thanks to the jetbrains chrome extension, it simply opened a new tab in chrome and launched my site in there with no problem whatsoever.
But recently I had to reboot my computer (with a beloved windows update) and now this is not working anymore.
When I start the debugging from webstorm chromes opens a new tab and I see the following in the address bar and then nothing...
data:text/html;base64,PCFET0NUWVBFIGh0bWw+PHRpdGxlPkxvYWRpbmcgaHR0cDovL3ZtLnNob3RndW4ubG9jYWwvPC90aXRsZT4=
My site is not opened and the page remains blank in chrome.
Most probably this is a result of Chrome update: some Chrome API changes introduced in v.37 break js debugger. WEB-12418 is fixed in WebStorm 9 EAP