I am experiencing a strange issue with AngularJS on a local (windows) environment. I use two bootstrap frameworks build with angular (homer and neuboard). When I run the template (both!) in its AngularJS version locally on windows Chrome freezes completely and causes a huge cpu activity. Firefox on the other hand works fine.
When I upload the same files (distributed template, now compilation neccessary) on my server both chrome and firefox are working fine!
Has anybody experienced something like that or a clue whats causing this?
I have one: Both use angulars ui-router. Maybe Chrome has in this case a problem with resolving/routing the URL, if it starts with file:///C:/...?
Kind regards,
Nico
I would try to check the dev tools in the browser. Check for errors and also the Network tab (https://developers.google.com/web/tools/chrome-devtools/)
You can precisely tell which operation took too long.
I sometimes had issues with cross-referencing on a local machine which is only an issue on some browsers (normally a useful security measure). There is a plugin to turn this off, if that is the error.
This issue is caused by chromes web security itself. By default chrome doesn't allow HTTP-Request from cross origins from other protocols than http, https, data, chrome and so on - but not from file:///
According to this question: Allow Google Chrome to use XMLHttpRequest to load a URL from a local file
I started chrome without Web Security and everything workes fine!
Related
I am writing an app in React in order to make a beautiful UI for my API. When I run it in Arch Linux's Firefox it works well. However, when I run it in my Android device, it seems like the initial API call (inside the useEffect of the App.js) is not done, not in Firefox neither in Chrome.
I am serving the app in the computer and then opening it with my local IP address (not localhost, obviously) with my phone.
Does anyone know why isn't that working in the phone even though it is working in my Linux machine?
The source code (of the UI and of the API) is in my Github (https://github.com/ToniIvars/Localdrive).
Thank you in advance.
I suffer a similar problem recently, may relate to unreachable IP address or some security problem.
I recommend using the chrome remote debug tool to make everything clear, in short that's how to do that:
First, open your phone debug mode, connect it to the PC with adb debug enable
Open chrome on your phone
Open chrome on your PC, go to 'chrome://inspect#devices'
Wait for a second and you should see your device, click inspect on it
Soon you can find out what cause the problem
Here's a full tutorial: https://developer.chrome.com/docs/devtools/remote-debugging/
I have a project using React but the component WebCam that works perfectly in all browsers locally; but when tested in a server, doesn't show the permits pop-up to allow the use of the camera.
I don't think the code is the problem. Instead some security on the browsers. I tried to give permissions directly to the site on Chrome and I can't change it. And is not blocked, on either browser.
Some other considerations:
I haven't install any ssl certificate, is just a small testing server to play, so I wasn't thinking to install them for the moment.
could this be the problem?
The getUserMedia API requires you to serve the page over HTTPS (or on localhost). So if you haven’t set that up, that is why it’s not working in production.
See the Security section of this documentation for more details: https://developer.mozilla.org/en-US/docs/Web/API/MediaDevices/getUserMedia#security
I have deployed a site via Google App Engine. The site is updated for all browsers expect for Chrome on Windows Desktop and Mac. Why is it so happening?
After a long time breaking my head on this problem finally I got the solution, the problem was very very very silly and irritating
The extensions attached to my browser namely Ad Block was causing the older version to be presented whenever I used to visit the site.
So the solution is:
Disable the extensions and see which silly extension is causing the trouble
We've got an Angular app that uses Auth0 for SSO login. We primarily use Macs and develop and test locally using the localhost web server. Browsing the site locally using browsers on Mac works fine. We can authenticate and the subsequent redirect does the right thing. The problem is browsing with IE. We can connect to the localhost web server on OS X using the IP address. We had to edit the Windows hosts file to map the Mac's IP address to localhost due to our app using full URLs/URIs as primary keys, so that the keys match.
When I browse the site using IE11 on Parallels, login using Auth0, it looks to authenticate just fine, but afterwards, we get an error when it tries to redirect:
XMLHttpRequest for https://mindjet.auth0.com/tokeninfo? required Cross Origin Resource Sharing (CORS).
Auth0 does have a field for specifying allowed CORS origins, and I tried every conceivable URL that our app exposes, even just *. But nothing worked. In our Angular app, I've tried setting $httpProvider.defaults.useXDomain = true; That didn't work either. I'm new to the CORS concept, so any insights would be greatly appreciated. We just want to find a way to test with IE without having to deploy to a dev server.
Our main issue that we couldn't test with IE11 seems to have been resolved by updating our auth0-angular and auth0-widget libraries to the latest version. I still occasionally see warnings about CORS issues in the console, but we are able to login and get redirected to the correct part of our app.
I'm trying to get a silverlight program to install locally and still be able to access wcf data services over ssl. When I run the application in browser, everything works fine. When I run the application out of browser without ssl everything works fine. When I run the application OoB with ssl, I get a "Not Found" error. When I run fiddler and retry, everything works fine. I'm guessing that the program isn't correctly decrypting or sending the ssl traffic when OoB since when fiddler does it for it, the application works fine. I'm also not hitting any exceptions or break points on the server when I attach VS to it (this makes me think there is a problem with the send). Any ideas on what my next step should be? Also, I am using a self signed certificate, could this be an issue? THANKS!
Has anyone found a resolution for this issue? Or does silverlight just not work with SSL in OOB mode??
See this link for reference:
http://msdn.microsoft.com/en-us/library/dd920295(v=vs.95).aspx
basically it says:
Client certificates are supported by the browser stack, but not by the
client stack. And there is currently an issue that (at least for our
application) prevents client certificates from working even with the
browser stack if you're in trusted out-of-browser mode.