Have not been able to use Chrome (Version 42.0.2311.90 (64-bit)) as a neo4j browser client after upgrading to the latest XCode / Command Tools in MacOS Yosemite 10.10.3 . Safari is working fine though. Is there an easy way to pinpoint to the actual problem? I'm using Neo4j 2.2.1
The following is a screenshot from the JavaScript console showing the errors:
mostly load resource errors and an uncaught error failing to instatiate module neo4jApp .
It works fine under Safari. It also works in a Chrome Incognito Window. Partially resetting settings is a trial and error exercise. While resetting all chrome settings finally solved the initial problem, I wonder if there is a better way and not having to lose all other user settings in Chrome.
I encountered the same exact issue today with Chromium 43.0.2357.81 (64-bit) and Neo4j 2.2.1. Clearing the cache and refreshing http://localhost:7474/browser/ wasn't working for me (javascript errors). What did work for me, was going to http://localhost:7474/webadmin/ which asked me to re-authenticate. After logging in, the Neo4j browser site loaded.
Related
I am having trouble debugging my web project using the Chrome Browser. I can only use IE to do my debugging. I did some "googling" to resolve this problem, and came across a few Microsoft threads that said to update to the latest version of VS2017, which I did. I use version 15.9.13 and Visual Studio 2017 tells me I am "up to date" when I check for further updates.
When I first updated VS 2017, it started working, and I could debug using Chrome (finally!). But now it has stopped working again.
I saw in other threads where people suggested deleting the .vs folder, which I did, but had no luck with that.
Google Chrome is up to date at Version 75.0.3770.100
I debug and run my application as "Administrator" so that shouldn't be the problem either. I also close all browsers before running the debugger, so Chrome isn't running elsewhere when I try to debug.
Is there any explanation why Chrome cannot launch when using debugger? I would really like to use Chrome because of it's superior "dev tools" and inspection tools. Any suggestions? Was sad to have it working only one day.
Having configured the same environment like yours(VS version and Chrome version) but can't reproduce the issue.I would think if something is broken in VS or maybe third-party extension is the causes this issue.
Please try:
VS repair and a reinstall of Chrome(don't forget to backup the bookmarks)
Uninstall or disable third-party vs extensions, this won't take effect until restart vs
Navigate to %LocalAppData%\Microsoft\VisualStudio\15.xxx directory, delete all ComponentModelCache folders in all 15.xxx folders.
Open your project in vs, changed the target browser from Chrome to IE. Then F5 and wait until it is finish. Stop it and change the browser back to Chrome. After that the error disappeared.
Also, create a new asp.net web app and debug it with Chrome browser to check if the issue persists. Hope it helps.
After upgrading to Chrome 56 on Mac, it seems that inline Chrome extensions no longer prompt an installation anywhere on the web.
Does anyone know why?
Console gives the following error message:
Uncaught Error: A Chrome Web Store installation is already pending.
at Installer.install (extensions::webstore:20)
at Object.install (extensions::webstore:82)
at installChromeExtensionm ((index):643)
at HTMLAnchorElement.onclick (VM1380 :1)
This seems to be an issue for all websites that have inline Chrome extensions (try grammarly.com, or momentumdash.com) - tested with multiple macbooks using Chrome 56.0.2924.87
I have a website http://kounj.web44.net whick works fine in all browsers.This week i noticed that my site would throw an "Aw,Snap " error on Chromium(Ubuntu 14.04 LTS 32bit).
I deleted every user but the problem remains.In other browser is working fine.Any ideas
Note.The problem appeared after upgrading my chromium browser to the latest version
UPDATE:
The problem was caused by a script for flare app and was resolved by removing the script
Not the users
Try restoring chrome to its default. This can be done in the settings options
I have a test written with intern that worked fine on Firefox and Chrome until recently - possibly until a recent upgrade of intern. The following code correctly tabbed to an element on the screen that can be focussed, and when actioned with the [Space] key would cause a script event to trigger.
.keys(specialKeys.Tab)
.keys(specialKeys["Space"])
.end()
If I do this activity manually in either browser it works fine.
Now when I run this sequence of commands it works fine in Firefox, but not in Chrome. I have tried forcing an update of both Chrome and ChromeDriver and running again. This has not fixed the problem.
Does anybody have any ideas as to why this is occurring?
I'm using intern 1.7, Chrome 34.0.1847.137 and ChromeDriver 2.10.0. If there is a particular sequence of npm commands that gives a reliable and stable installation when one of the afore mentioned components upgrades that would be very useful.
This is a known issue with Chrome 34, caused by keyboard focus being stuck on the address bar. It is not a bug in Intern. More information can be found at https://code.google.com/p/chromedriver/issues/detail?id=762.
To test the use NUnit + Telerik Framework
Browser: Google Chrome v24 + standard extension of Telerik
When you run the test - an error "Failed SetUp: System.IO.FileNotFoundException: Chrome browser is not installed on this machine TearDown: System.NullReferenc"
Reinstall Telerik and Google Chrome did not help.
Tell me, please, how to solve the problem?
Translated by Google Translate.
Issue resolved.
Cause of error - Telerik does not work with Google Chrome v.24
Installed Chrome v.20 - it worked
UPD:
After the automatic browser update to version 24 - Telerik is working correctly
Re-install chrome, and do not say yes to the UAC prompt. What is most likely happening if chrome was installed with admin privileges so it installed to program files. Telerik's testing framework expects chrome to be installed in %appdata%. By saying no to the UAC prompt and yes to the install without admin prompt chrome will revert back to installing in %appdata%