Chrome Inspect Element crashing with Ripple Emulator - google-chrome

I'm building a mobile application with Visual Studio 2013, using Ripple Emulator and Cordova.
Every time that I try to inspect an element (hitting Ctrl + Shift + I, F12 or right clicking the page and selecting Inspect element) the Google Chrome closes and Visual Studio stops running the application.
Has anyone know why I'm unable to inspect elements inside the browser using Ripple Emulator?
Ps: Visual Studio 2013 has his own DOM Explorer but the experience is not the same as the Chrome Developer Tools.

A simple workaround is to start your project without debugging (Ctrl+F5) from Visual Studio. This will allow you to use the Chrome dev tools (F12 and so on) without killing the VS debugger process and therefore stopping your Ripple session.

I've been having the same issue since upgrading to cordova tools update 3 with visual studio 2015 community edition - it was working fine before "upgrading"
I haven't found a reason why, but there is a workaround which is to start your debugging session (F5.. or whatever) then hop back to visual studio, then select "Detach All" from the debug menu. This, or use a different browser (Edge works fine in Windows 10, but I'm not used to it's interface).
Hope that helps.

There was a change in the chrome debugging API that prevents VS from inspecting the elements and changing the style. Chrome version 43 will work. You have to take some steps to keep it from auto updating. The installer for chrome 43 is here:
https://dl.google.com/chrome/win/4ED6DD719811795B/43.0.2357.134_chrome_installer.exe
You will need to uninstall chrome, update the registry, then install chrome 43. When you go to the about screen it should say updates have been disabled by the administrator.
Here are the registry changes:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Update]
"Update{8A69D345-D564-463C-AFF1-A69D9E530F96}"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Policies\Google\Update]
"Update{8A69D345-D564-463C-AFF1-A69D9E530F96}"=dword:00000000
This thread has more information on the changes needed to the registry to prevent the auto update:
cannot stop Chrome from updating from 43 to 44
NOTE: this means you are not getting security updates on that install, only use this until the issue has been resolved in an upcoming patch.

Related

Ubuntu 20.04 - After suspense problem in chrome browser tabs

Ubuntu 20.04 - After suspense problem in chrome browser tabs, The tabs displayed with strange dots(like sand).It happens as well in visual studio code.
Go to the Chrome main menu (3 dots on the top right corner) → More Tools → Task Manager.
Sort by process Task name.
Find the process called GPU Process.
Click on End process.

VS2017 Chrome Browser Debugger "Object reference not set to the instance of an object"

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.

Chrome Developer Tools: Missing "Resources" Tab

I am running Chrome Version 52.0.2743.116 (64-bit) on OS X 10.11.3 and upon trying to debug a website realized that the Resources tab in my Developer Tools is just completely gone. What gives / has anyone else noticed this?
"The Resources panel has been renamed to the Application panel. All of the features from the Resources panel are still available in the Application panel."
from https://developers.google.com/web/tools/chrome-devtools/iterate/manage-data/?hl=en

Tizen doesn't recognize Google Chrome

I just bought a Samsung gear 2 neo and wanted to create my own watch. So this means I am new to Tizen development.
I installed the Tizen IDE and the SDK but for some reason after following -a part- this tutorial (http://www.slideshare.net/badaindonesia/professional-tizen-application-development) Tizen won't run my projects because it can't find Google Chrome on the specified location. This problem occures when I try to run a Tizen web application as a Tizen web simulator app. When i try to launch it as a Tizen web app it says Could not find emulator or device but that isn't my current target.
The specific message is Google Chrome could not be found (C:\Program Files(x86)\Google\Chrome\Application\Chrome.exe). Please install Google Chrome and specify the Google Chrome program location in Window->Preferences under "Tizen SDK/Web/Simulator".
I have tried changing the location to C:\Program Files(x86)\Google\Chrome\Application\ But this wouldn't help either. Yes, i have entered the correct location since i have manually located the chrome.exe to.
The only thing which might be wrong is that I am using the Windows 7 64 bit installer while I am on a Windows 8 64 bit desktop pc.
I have experienced a similar bug. Maybe this will help you/future developers:
My problem was that the Chrome app wouldn't open while pressing debug. I subsequently tried it with the Visual Studio Tizen extension: same problem.
The fix: I dove into the extension code and found that changing the chrome path via the option "Change Chrome path" doesn't actually change your chrome path.
What does? Going into "C:\Users\[USERNAME]\.vscode\extensions\tizenweb.wappl-1.1.2\lib\constants.js" and changing Constants.CHROME_PATH to your chrome path (for the operating system you are using).
I have not found a solution for the Tizen app, though I would recommend using the VScode extension anyway.
I had the same problem. Though not exactly a solution, I found a workaround.
Start the Web Simulator from Start Menu
Enter the location of your index.html file in the address field and press Enter
Don't forget to add file:/// in the front.
There you go!!

How to close Netbeans html debug Chrome connection when silent mode is on?

As I stated in the title, how does one close (temporarily disables) debugging session connection Netbeans 7.4 with Chrome browser. The browser has flag #silent-debugger-extension-api turned on and Netbeans connector extension installed. Sometimes I have to turn off debugging because Netbeans CSS window does not show browser native styles, which is confusing. Thank you from the mountain! ;)
Simply open Chrome Developer Tools in given page. It terminates session between NetBeans and Chrome because only 1 degbugger can debug page - either Chrome Dev Tools or NetBeans. Once you close Chrome Developer Tools, re-run your project/file from NetBeans to get debugging with NetBeans back.