I'm creating a website using Angular.js and have primarily been building it using Chrome, but now I have gone to test some features in Safari (on OSX Mavericks, safari Version 7.0.1) and when I try to open the developer tools they keep crashing or are un responsive.
I have tried various methods of loading up the dev tools and none of them seem to work. For example, opening the dev tools by right clicking on an element and clicking inspect element doesn't work, and neither does opening the console via the Developer tab.
I have tried disabling extensions, but that had no effect.
If anyone has any ideas I would be extremely grateful!
So it looks like since safari has been upgraded to 7.0.2 this issue has been fixed. It seems that the devtools now work completely fine.
Related
while developing a react application on vite, on ubuntu system,
I've encountered an infinite loading of app when try to run it in google chrome.
On the other hand when I start it in firefox it works fine.
May be somebody encountered such a problem and knows a way how to resolve this kind of problem?
This happens only on Linux sys, on Mac or Windows application runs without problems in Chrome Browser.
I tried to increase the limit of watchers of ubuntu system to maximum, but this doesn't help.
I tried to remove all chrome extensions + react dev tools - doesn't help.
I tried to find some information related to this problem in internet, but I can't find any usefull information, that's why i ask you guys. May be somebody knows how to cure this behavior )
While the web code has not changed, my selenium automation tests are unable to find some xpaths today. I am not sure if there was an update? Has anyone else noticed this? I have went back, inspected the elements (all links), and tried different xpaths, and nothing is working.
This is usually because of an upgrade to Chrome. The ChromeDriver can only support certain versions.
I can see that actually, within the past few days, Chrome has updated to v33:
http://googlechromereleases.blogspot.fr/2014/02/stable-channel-update_20.html
So I'd suggest you download the latest ChromeDriver from here:
http://chromedriver.storage.googleapis.com/index.html?path=2.9/
I'm working with a Silverlight 3 app and using Chrome as my test browser. While debugging I keep getting the popup message:
Plug-in Unresponsive
The following plug-in is unresponsive:
Unknown Would you like to stop i?
Yes/No
How can I turn this off in Chrome? Can VS be set to shut it off only when debugging? It's a real pain when debugging.
Thanks,
Add --disable-hang-monitor to chrome shortcut
Nick - are you using Chrome early builds on the Mac? There are some known issues with Chrome/Silverlight that we are working through with the teams -- most scenarios work though. Is this something you can share so others may verify?
To be honest, I set IE9 as my default browser when debugging Silverlight and switch back to Chrome afterwards. Chrome doesn't seem to communicate to Visual Studio (or vice versa) so I can't get breakpoint and exception information when using Chrome.
Does anyone know how to debug a Silverlight 2 app running in Google Chrome from Visual Studio? Even after making sure that Chrome is the debugging browser, breakpoints are still not being hit.
Have you tried attaching to Chrome manually? Tools > Attach to process?
Chrome isn't officially supported but there are hacks.
Here for example. Halo's comment may give you some help too.
You can have more than one browser running on your localhost.
1) Hit F5 to run debug. Probably opens IE or whatever your default is. F5 your way through the breakpoints until it's loaded. Leave this IE open.
2) Open your other browser, coping the localhost Url into the new browser and run it. New browser should hit the breakpoints.
This works with all browsers, and even emulators like BlackBerry emulators.
Attach to the process manually (Tools > Attach to process), but make sure to attach to the chrome process that lists its type as "Silverlight, ...". Its title should be blank.
If you see your application name in the title, it's because chrome has a separate process for the HTML form that your Silverlight app is in, and the html's title probably matches. Attaching to this process does not load the Silverlight assemblies.
I usually will start debugging the app in IE to make sure that the most recent changes are compiled and running, then launch chrome, clear its cache ('cause it likes to hang onto Silverlight data), paste in the url from IE, and then stop IE and attach to chrome. Extra steps, but worth not spending 3 hours to figure out you are looking at cached assemblies.
This is an issue with Visual Studio interacting with Chrome: http://code.google.com/p/chromium/issues/detail?id=45560. My guess is you need to wait for a Visual Studio patch, but I honestly wouldn't hold your breath. The majority of Silverlight developers just use IE or FF for debugging. (Apparently even FF has some issues now that they've sandboxed their plugins: http://timheuer.com/blog/archive/2010/08/16/enable-silverlight-debugging-in-firefox-visual-studio.aspx#20476). As much as I hate IE, it's really your best bet for debugging Silverlight apps.
Simply set SL app as startup prtoject instead of asp.net and press F5
Does anyone know if silverlight plugs into chrome, or when they plan to support it?
This guy have had partial success with silverlight in chrome, but it does not seem to be supported:
http://wildermuth.com/2008/09/02/Silverlight_2_and_Google_Chrome
From The Microsoft Silverlight Team in the silverlight forum:
Hello, currently we don't have plans
to support Chrome. We will support it
in the future if it gains enough
market share. Please understand, each
browser implements the plug-in model
differently, so it'll be a lot of
effort to officially support a browser
100%... By the way, IE 8 also runs
each tab in its own process. If a tab
crashes, other tabs will still work
fine.
UPDATE:
Jon Galloway has just posted instructions on how to get silverlight successfully running on Chrome here:
http://weblogs.asp.net/jgalloway/archive/2008/09/17/silverlight-on-chrome.aspx
The official word on what is supported looks like this:
alt text http://www.jesseliberty.com/sl/browsers.jpg
The reality is that we do run on a lot of browsers, but things change might quickly in these here parts.
For what it is worth, the Dev Branch of Google Chrome was recently updated to support Silverlight 2. I tried it and it works for me. Of course, you have to use the Dev release of Google Chrome. You can get more information about switching to Chrome Dev here.
Silverlight already works with web-kit, and since Google's Chrome is based on web-kit, it shouldn't be too much effort to get it working.
Indeed, this gentleman seems to have had some success.
Based on this, I would suspect that Silverlight will be fully supported by Chrome by the time it goes gold.