I'm having an issue with getting Chrome's Developer Tools to work on my machine.
I've tried both Chrome Version 37.0.2026.0 canary and Version 35.0.1916.114 m and both have slightly different problems - I'm using Windows 8.1.
In the standard installation of Chrome, the Developer Tools options are greyed out. I've searched this everywhere and there is a Google post saying to enable it in your registry settings. When I go into my registry, there is nothing relating to Google in the path they've specified - [http://www.chromium.org/administrators/policy-list-3#DeveloperToolsDisabled][1]
In the Canary version of Chrome, the Developer Tools options appear and are not greyed out or anything, but absolutely nothing appears when I click it (no window, no error, nothing).
Anyone have any ideas? I've tried restarting the machine, clearing my cache, reinstalling Chrome but no solution..
I'll keep looking for a solution and post it if I find anything!
Thanks in advanced.
Ohhhh! I went through my Chrome settings again and noticed that Javascript was being "enforced by my administrator"
I figured out what it was (so stupid): We use Google Apps where I work and it's been disabled in the Admin Console. You definitely pointed me in the right direction though!
Related
I am attempting to use google docs with firefox, but am constantly getting this message.
It never goes away.
And if I close the tab all of my work is deleted.
This is a brand new Firefox install.
Is this an attempt to force us back to using chrome with google docs?
I have been a chrome user for many years but was recently forced to switch to firefox because chrome has an intolerable bug on macOS catalina.
I need to use google docs but I can't use chrome because of this chrome bug and now I can't use firefox because of this bug with google docs.
Is there a work-around for the problem?
Chrome allows me to work with local copies of google docs without losing work if I lose my network connection, but I cannot find a similar plugin for firefox.
I tried to reproduce the issue on Firefox, however it seems to work fine at my end without any sort of error or warning popup in saving.
But, Google is known to play nasty with competitors to promote Chrome and it can't be ruled out that it might be a cause too. You can try multiple options, and check which one works.
Possible Solutions:
If you want to trick google into thinking you are browsing on Chrome, change this setting in Firefox as mentioned here!
Try using the Firefox Developer Edition: [Official Link])(https://www.mozilla.org/en-US/firefox/developer/ "Firefox Developer Edition")
If the above options don't work, try switching to Microsoft Edge for a Chrome alternative if the bug is particularly associated with Google Chrome, though they both are based on Chromium, it's worth a try.
Searching through the Google forums, I came across an issue with GDrive not loading in Firefox. https://support.google.com/drive/thread/1987396?hl=en&msgid=22679169
The last comment on the page the user mentions disabling CORS
Find a solution ! When the add-in CORS (Access-control-Allow-Origin)
is enabled impossible to load the google drive page but no problem
when it is deactivated.
Have you tried disabling the CORS? http://testingfreak.com/how-to-fix-cross-origin-request-security-cors-error-in-firefox-chrome-and-ie/
This will happen if you try to copy/paste info from a place that is restricted. Make sure editing is turned on for all users. If it’s not “shared” correctly it will glitch.
General Problem
We've had a long-standing problem with our two ExtJS 5.1.0 apps that div scrollbars don't show in Chrome, using only our QA testers' AWS Workspace Chrome browsers. They don't see this in other websites using that Chrome, only our two applications. We've been able to ignore this since the problem was isolated, but now a user is having the same problem.
We've been able to confirm that the difference is that wherever there's a div that should be overflow: auto is being generated as overflow: hidden. So scrollbars for grids, dropdowns, etc don't render but the div can still be scrolled via other means (tabbing, page down).
I've been looking for general ideas about what could cause this--is it ExtJS? Windows setting? Chrome setting? Again, the problem is isolated to AWS Workspace's Chrome and a user's Chrome.
Versions
Chrome:
AWS Workspace has exact same Chrome version as me, 79.0.3945.88.
User has Chrome 80.0.3987.149 (up-to-date).
Windows:
AWS Workspace is Windows Server 2016 Datacenter.
User has Windows 10.
What We've Tried
These are all troubleshooting steps we've tried in the AWS Workspace Chrome:
Disabled all extensions. Also ran in incognito mode which should do this also. The extensions are nothing that I don't also have, and I don't see the problem.
Inspected Chrome's flags--they're all default, and again not different than what I have.
Disabled Chrome's “Use hardware acceleration when available” setting and restarted Chrome.
Previously opened a ticket up with AWS and they were unable to help.
Researched any connection of this to Chrome, ExtJS, or Windows Server 2016 Datacenter without luck. Only found general information about "what to do if you have scrolling problems in Chrome".
Other Problems Our Apps Have in AWS Workspace Chrome
Listing these in case it helps trigger any ideas about the underlying problem, but focusing on the scrolling for now. Again these are isolated to Chrome in AWS Workspace (unclear if the user is seeing these also):
Drag and drop doesn't work.
Tabs that aren't the selected tab when the tab bar is loaded don't load at all.
It turns out that the problem was related to touchscreens. Our user has a touchscreen laptop (and didn't realize it for a while, we asked about this early on). And the Amazon Workspaces are touchscreen-compatible, as they have a "HID compliant touch screen" device listed in Device Manager > Human Interface Devices. So something about touchscreens + Chrome/Edge is telling ExtJS 5.1.0 that the device is mobile and scrollbars shouldn't be rendered.
Solutions:
For our user, she was happy to disable her touchscreen device and this worked for her.
For Amazon Workspaces, disabling the touchscreen device did not work. For Chrome we were able to resolve by adding --touch-events=enabled to the Chrome shortcut. There are various touch-related Chrome flags mentioned online as a solution, but none of those are available in the current version. Anything touch-related we did find in Chrome's list of flags didn't help.
I haven't looked for a solution for Edge if someone uses Edge and wants to keep their touchscreen. This is fine for us right now. (Because we realized Edge has the problem also, presumably due to Chromium. Did not see it with Firefox.)
And I did confirm using ExtJs' Kitchen Sink examples that I can replicate the problem in 5.1.0 with both a touchscreen laptop and an Amazon Workspace. Also that I can't replicate the problem in the current version, so we should be good once we upgrade.
I'm using Version 80.0.3987.116 (Official Build) (64-bit) on Microsoft Windows [Version 10.0.17134.1304]. The Chrome Developer Tools simply do not appear for me no matter which way I try to access them:
ctrl+shift+i
f12
ctrl+shift+j to open the last used panel
ctrl+shift+c to open the elements panel
right click on a web page and select inspect from the popup
menu dots menu -> more tools ->
developer tools
I've restarted my computer. I've gone into settings -> advanced settings and restored all settings to their original defaults, then restarted chrome. This disables all extensions, so even with all extensions disabled it still didn't display. I've cleared the cache.
It was all working last Friday, but not when I tried Monday.
Has anyone seen this or have any other troubleshooting ideas? The only other thing I can think of is uninstall with something like Revo Uninstaller to scrape the registry and filesystem, then in my profile zip up then delete %userprofile%\AppData\Local\Google and %userprofile%\AppData\Roaming\Google. That seems extreme if there's an easier way.
Anyone seen anything similar?
Thanks!
I feel stupid figuring this out so quickly after posting the question. But if anyone else finds this, here's what worked for me.
ctrl+t to open a new tab
enter chrome://flags/ in the address bar
click reset all to default
let chrome restart
I'm not sure which flag was set that caused this. When I searched for devtools, there were three available settings, and they were all set to either disabled or default. And that's what they were after I did a reset all too. So whatever broke it was some other setting.
I'm confused I don't know if the latest update of chrome AKA version 73 just integrated this attribute on purpose but I'm getting a strange attribute that I did not added into my web pages and i'm wondering what this means in chrome?
CHROME BROWSER
EDGE BROWSER
Should I be concern with this? It's only showing on Chrome.
There is another Chrome and Firefox plugin that does same, sadly, but probably one of best VPN tools Urban VPN Browser Extension. The solution is same, just deactivate. Btw, those guys have other extensions, haven't tested others.
Just uninstall any type of VPN that you installed in you browser and afterwards bis_skin_checked="1" will removed automatically.
The attribute is added just because of one of an extension of the Chrome Browser you have installed in your Chrome Browser. I also got this attribute added to my HTML when checking in the console. Then I replicate this by deactivating extensions one by one and found it's adding from Hover Over extension.
This problem has happened to me recently. I installed the Urban VPN plugin and after that, I faced this issue. But uninstalling the plugin, the problem is solved.
I've got the SpeakIt! [Version 0.3.20] extension installed for Chrome [Version 74.0.3729.131 (Official Build) (64-bit)] on Windows 10, and I am seeing the same bis_skin_checked="1" when it's enabled. When I disable the SpeakIt! extension, the bis_skin_checked="1" goes away.
This thing append from different Chrome/Mozilla extension.
Disable recent extensions to see the changes(bis_skin_checked="1" goes away
).
So i have been running into this problem with a lot of Wordpress sites lately, usually occurring when i am logged in as Admin, so i couldn't post here because no one would be able to view the problem. However, i just found a site that it happens on that doesn't require admin creds.
http://www.otisports.com/
When i visit this site in Chrome (Version 34.0.1847.137 m), it just displays a blank page. No errors, just the (what now seems standard) event.returnValue is deprecated. Please use the standard event.preventDefault() instead. warning. I have seen that warning signify problems on the site, but they are usually minor, not to the extent that the above URL displays. However, if i open an Incognito window and visit the site everything works perfectly and there is no warning. Does the Incognito window deal with webpages in a way that is so entirely different that it would cause something like this to happen?
I have been racking my brain trying to figure this out. Can anyone reproduce this? is it a bug in chrome?
EDIT: I just tried to open a bounty on this question and the EXACT same thing happened. In Regular Chrome, nothing happened when i clicked the start a bounty link and i saw various errors Undefined is not a function however in incognito everything worked perfectly. what gives?!
EDIT: Yes, i have cleared the cache, history, cookies, everything, and i still get the same errors. I cant even post a comment on this question because of errors...
I came across the same issue when trying to open evernote.com. It loaded successfully while using incognito mode in chrome. Let me share how I fixed this even though the original post is way too old. But maybe someone can find it useful.
I'm using chrome (Version 73.0.3683.103 (Official Build) (64-bit)) running on Linux Ubuntu 18.04.2 LTS.
I tried disabling all extensions and clearing browser data/cache but nothing worked. PS: Disabling adblock previously worked for me. Yes, I stumbled over the same issue before and whitelisting evernote in adblock solved the issue. But it didn't now.
The following is what worked for me:
Open developers tools (CTRL + SHIFT + J).
Navigate to Applications tab.
Choose Clear storage from the side menu
Hit Clear site data button.
After reading the comments I dug into chrome and saw there was a bunch of extensions still sitting around that were definitely malware and I thought I had previously deleted. Instead of picking through them one-by-one, I just deleted everything, re-installed Chrome, and now everything works great!
I had the same issue. My application was working in Incognito mode and in Firefox but not in Regular Chrome. I even disabled all the extensions but no luck. I eventually cleared the Cached images and files because on developer console I found out that the regular chrome was still picking up the old file due to caching. So as soon as I cleared it, my app showed up like a rocket :)
Try removing any non required extension .
Specifically AdBlock
I resolved the problem post that.
Since on Incognito , extensions are disabled, hence page run as expected.
I resolved this unforeseen issue using following steps.
CTRL + SHIFT + DEL > Clear Browsing Data.
Cookies and other site data
Cached images and files
This is for Chrome Browser.
Open Console (Ctl+Shift+I) first.
Then under the application tab, you will find some options on the left, find out the application there, you will find it at the top.
There you will find Service Workers.
Under Service Workers, there will be three checkboxes. Select Update on reload checkbox and reload again.
I had the same issue after installing React-Sight Extention.
The Page hanged but not in the incognito mode.
Try deleting any recently added or junk extension.
Delete your cache.
That worked for me
I had a similar issue in chrome, in my case the problem was that I could log in to my university library's website only in incognito mode. After some digging, I figured out that Google Translate extension was set to automatically translate any page. When I turned that off and instead selected never translate that specific page, it started working in the usual mode as well.
This is rather an old issue but still happens. None of the solutions recommended here and there did not solve the issue in my case.
I somehow noticed this is related with a -some kind of- corruption on the user profile.
This is how I solved it:
Close all Chrome browsers.
Open a Google page on Chrome.
Sign-out from Google (rigt click your profile picture on a Google page, not on the Chrome itself), and sign-in.
If this doesn't work:
Close all Chrome browsers.
Right click Chrome icon and select Google Chrome.
Delete your Google profile on the "select your profile" page.
Close Chrome.
Open Chrome, sign-in.
uBlock Origin was the culprit in my case. Once I allowed the site in uBlock Origin, pages loaded correctly in normal Chrome.