Every time I start up a new instance of IE8 32bit, Developer Tools opens automatically. How to disable that and keep F12 functional?
I have tried searching for and deleting all registry keys named IEDevTools (including under HKCU, HKLM, 64bit and 32bit registry). I have also tried adding a DWORD named Disabled, valued 1, at the single location, under HKCU, that gets recreated by IE start-up.
None of that helped. This is a Windows 7 64bit system that has seen multiple up- and downgrades between IE8 and IE9, and also has Chrome and Firefox. (I have seen interaction between Chrome settings and IE settings before, but I can hardly imagine one here.)
People who just want to put F12 to another use, which is not my case, please find your help here.
Well, in my case the following procedure did the trick:
Pin the developer tools window by pressing the small button in the top right corner of the window.
Close the developer tools by clicking on the close button in the top right corner of the docked tools zone.
Now, when you open a new instance / a new tab of IE8, the tools don't come up anymore. It seems that they keep opening when you close an instance of IE8 with the tools active and unpinned (on a separate window).
Hope this works.
I did not figure out the cause, but this is how I got over this in case anyone wonders: IE8 64bit works on the same system without a problem.
(In a next step I had to move on to IE9 because IE8 64bit is not compatible with SharePoint. Yet another step will follow after the last few IE only apps that I still need to use die out.)
Related
Probably some of you faced similar problem of Safari dev tools.
When I debug CSS properties of elements on Safari dev tools, it's fine - I can enable/disable different properties and they're get commented/uncommented (see attached picture), but when I start debugging iPad pages remotely - it's different...
When I disable some CSS property, it disappears instead of getting commented. I have no other possibility to enable it. I must add it manually... It's annoying...
Do you know the solution?
I think I found a solution. I use iPad 4 which has no more iOS updates available (last one is ver.11).
However I could get rid of the problem by going to dev tools settings, selecting experimental tab and checking the "Legacy style editor" checkbox
I hope it will help someone of you.
I have the Piczard SimpleImageUploader in a asp.net based management tool for a product catalog that seems to work just fine for most users, but for some users, the Edit popup will show, but then the image does not load. The logo and progress will just stay there and never move. Users are typically in IE 11 on a Windows 7 PC. We have tried in other browsers, but FF and Chrome seem to not allow the popup at all, probably due to the branching of Flash, which Piczard seems to need to run.
Could there be a setting in IE that is blocking the image from uploading? The tool worked just fine for the user a few months ago, but recently has not be cooperating. I was thinking it could be a Group Policy, but I have not been able to confirm that yet.
Any leads are appreciated.
Windows updates, IE Advanced settings Reset and a reboot fixed the problem this time. I do not know which setting or update fixed the issue at this point, just that it did. I had done the reset before but that alone was not enough to fix the problem.
I have a problem with the inspector in Firefox browser. After some time of use, in the "rules" tab, system don't want to show me CSS syntax suggestions. After switching the inspector off and on, everything returns back to normal, but ... again ... after a few moments, the system stops showing me syntax hints.
with syntax hints without syntax hints
after a couple of minutes
Is there any FIX for this? I'm using newest "FireFox Developer Edition" (same thing on normal "Firefox").
UPDATE:
I discovered that inspector starts to work improperly when I restart a page which I have been "inspecting".
Are you using Firefox Developer Edition 41.0a2? It appears to have possibly been a bug that is being corrected.
I can confirm this happens in Firefox 40.0.2.
I also saw this in Firefox Developer Edition 41.0a2.
I updated Firefox Developer Edition to 42.0a2 and am no longer able to recreate this phenomenon.
Install firebug plugin for firefox. Ita a very good debugger tool. After installing enable it and right click on page and do "inspect element with firebug"
I have an application with crystal reports which I've just noticed has a fairly large issue. The treeview/drill-down menu on the left will not display in Internet Explorer, however it does work with other browsers (chrome/firefox/etc.). I've never used CR before (these are actually inherited, I haven't touched them), but I'm guessing it's an IE option that's not set some where. Any idea how to fix this?
EDIT:
Per the question about browser version, I am working with IE8. I did notice that when compatibility mode was turned off, it displays as I would expect. However, the app is supposed to handle IE7 (which I do not have access to) as well.
I've noticed a strange behavior in two different sites when using IE8.
The first site is in the site that I maintain xebra.com.
The second site is google analytics.
The behavior is that when an address is typed directly into the address bar of IE8, both sites display correctly,
But when one of the sites has already been loaded, and you press the refresh button or F5 key, the layout gets all screwed up:
See screenshots here: here
Something is causing IE8 to render in 'quirks mode' which causes the breakage.
You can duplicate this by browsing to your site in IE8 and selecting Tools > Developer Tools > Document Mode > Quirks Mode.
Make sure your document is always being served in standards mode.
EDIT My original answer had 'compatability mode' where it should have read 'quirks mode' - the two are different.
JS.Companion was what was causing this odd bug, and not IE8. Phew!
http://www.my-debugbar.com/wiki/CompanionJS/HomePage
I spent the whole morning trying to figure out what was going on, I removed companion.js and bingo my site is perfect! thanks for this.
That's really strange. I don't have the problem on my computer with Companion.JS installed and http://www.xebra.com/ web page (under Vista SP1).
I would be happyto correct the Companion.JS bug that generates this problem if you can provide more information about the problem.