Is there any circumstance that would cause IE9 to force an unrequested page reload? If so how can I tell that this is occurring? Is there a log I can look at or custom event I should be looking for in event viewer?
I am troubleshooting an issue with an AngularJS web application that only exists in IE9, it works fine in newer version of IE and works on FF, Safari, Chrome. When testing in IE9 I see no errors in the console but I am getting redirected to my applications login page. This redirection always happens on a page reload, hence why I think IE9 is forcing a page reload.
You can track navigation events, and the subsystems that invoke them, using the Network tool in Internet Explorer 9's F12 developer suite. Press F12, switch to the Network tab, and press "Start Capturing". From this point on, any further navigation events will be logged for your inspection.
Internet Explorer 9 uses an older version of the F12 developer tools, but you can still access the historical documentation for those on the Microsoft Developer Network.
The modern documentation for IE 11 is also available online, and much of what is shared about the Network tool in particular is still helpful even if you happen to be using Internet Explorer 9.
Related
I'm currently working on an issue with a Microsoft Edge Add-In written in React in which state changes aren't working, and I can't see any of my console logs.
Some context:
I have a web Add-In for Microsoft Outlook desktop that I am trying to run on Windows 10 version 1903. I've added console logs to the event handlers of a few button clicks and several other events throughout the app, but none of these console logs actually show up in the Microsoft Edge DevTools console. I can see calls to console.log('We just clicked a button') in the compiled JavaScript file in the Debugger, so my changes are being picked up and are in fact there, but no actual console logs show up inside of the DevTools console. The only error I see in DevTools is XML5632: Only one root element is allowed on index.html (1, 1).
I should note that the web Add-In works in Microsoft Outlook desktop on later versions of Windows 10, but running it on version 1903 is the only time that it's problematic.
An answer on this forum: https://www.outsystems.com/forums/discussion/20753/xml5632-only-one-root-element-is-allowed-error-on-windows-edge/#Post88600 suggests it's a problem with Edge interpreting an Ajax call as XML, but doesn't elaborate much more beyond that.
My guess is that this a JavaScript issue with pre-Chromium Edge, but I'd like to know if anyone has any suggestions on a workaround or fix so that I can 1.) Resolve the issue with the state change in my React app and 2.) See my console logs.
I was executing webextension on Firefox for testing with about:debugging menu.
Then tests are done, I want to stop it.
I am looking for a way to stop without shutdown browser, but I can't find a way to stop it out.
Is there way for do it without shutdown browser?
Just like a normal add-on, you can disable or remove a temporary WebExtension that was loaded from about:debuging from about:addons (Ctrl-Shift-A, or Cmd-Shift-A on OSX) . If you "Remove" it, and then refresh about:debugging you will see that it is gone from that list.
If you do not refresh about:debugging after disabling or removing it, it will remain in the list that is displayed. This can be convenient if you are testing behavior when the add-on is installed or removed.
The following gif shows loading and removing an add-on named "aaaaaaaaaaaaaaaaaa - demo add-on":
If you do not refresh about:addons after removing an add-on, the add-on will remain in the "uninstalling" state. From that state you can "Undo" the removal/uninstall. This is displayed in about:addons with the "Undo" link. The fact that an extension is in this state is not available to WebExtension add-ons, but can be seen from other Firefox add-ons using the Add-on Manager API. The Add-on Manager API is not compatible with WebExtensions. If you want to take a look at a Firefox Add-on SDK based add-on that shows these states, you can see my answer to another question.
We are having problem with a Silverlight 5 app and IE11.
Suddenly, it's no longer possible to copy-and-paste from a Silverlight application to the clipboard, after upgrading to IE11.
When the Silverlight dialog that asks you for the right to access the clip-board appears, then IE11 freezes. This behaviour has also been verified on IE11 och two different Win 8.1 computers.
We have also tried to add the site to trusted sites, and 'Allow programatic access to clipboard" to Enabled. But it dosnt help.
Any suggestions?
Anyone knowing if this is something Microsoft is addressing?
/Erik
Ran into the same issue, running IE as administrator ended up clearing up the freezing issue.
From there you can then check the box to [remember my answer], click [yes] to allow clipboard access for this site, then restart IE (non-admin) and it won't freeze when accessing the clipboard.
I have a website running on dotnetnuke. However, recently I can't do any action (edit content or page setting) on certain pages (the products subpges in www.midoco.com). Does anybody know why this happen?
What version of DotNetNuke are you on? Check the HOST SETTINGS page to see if you are using the HOSTED Jquery option, if so, try disabling that option.
It is probably a javascript issue, try firing up chrome developer tools (hit F12 in chrome) and check if you have a red X in the bottom right corner. If so, click it and check what causes the issue. I had some similar issues caused by single quotes insted of apostrophes in a language pack and spent a lot of time to find the issue. I just went to one of the pages and see you have an error in /engine1/script.js in your skin.
Can anybody tell How to debug application in extjs in internet explorer and google chrome Browser? is it possible using Breakpoints to debug to check the values?
Thanks
There is a good article provided by sencha. check the section for internet explorer, http://www.sencha.com/learn/debugging-ext-js-applications
I have been forced to use IE8 in an application which works in Chrome and Firefox but fails often in IE8.
Debugging ExtJS in IE8 is nearly impossible if the problem is in the framework. IE8's developer tools hangs loading ext-all-dev.js
Also you can't get stack trace as in Chrome.
I had to put alert() calls in suspect lines and the whole process is a nightmare.
If you can avoid IE, do it.
Else be VERY VERY patient...
You can use the Developer Tools for your browsers. I don't use IE but I use Chrome's Developer Tools all the time! And yes you can do breakpoints, check values, etc..