I'm trying to open my live server in Chrome but it keeps defaulting to Chromium, no idea why or where it even pulls it from since I only have chrome installed.
Chromium was working at first but it doesn't seem to handle CSS-grid and I need that now.
Related
I installed selenium and used a python program to run chrome using selenium on my MacBook Air. Before there was an error on selenium, and after installing googlechrome drivers for selenium and creating a PATH using terminal, it opened a separate google chrome page that showed Chrome is being controlled by automated test software.
After around 30 minutes of running python and using selenium, I saved and closed out of everything.
In the next 2 minutes, I reopened Google Chrome to search something about web scraping, and the browser was the same one used by selenium. It still showed the Chrome is being controlled by automated test software notice, and there was a Chrome Automation Extension.
I tried:
logging in and syncing, but syncing was not available.
opening Google Chrome from application folder and dock, but nothing changed
deleting Google Chrome and reinstalling, but nothing changed
I don't know how to fix this. Can anyone help me?
Thanks in advance!
Ok, so I found out that the chromedriver was still running in the background. After I closed it using activity monitor, the problem was solved.
When Chrome starts in debug mode from VSCode not text is displayed. When Chrome is started from from the normal the normal link it displays the site correctly. When the developer tools in Chrome is opened no text is displayed.
Situation occurs since last week.
Google Chrome is up-to-date
Versie 67.0.3396.87 (Officiële build) (64-bits)
I have tried to clear caches and even reinstalled Chrome, but until now no succes.
Image of fault situation Chrome launched from VSCode
Image of desired situation Chrome started normally on same machine
Can someone please shed some light or point me in a different direction.
We are using adobe flash that launches an app inside of a JSP. Up until yesterday everything was running fine without any issues. Today when the Flash Object launches you can see the initialize bar where before you hardly seen it.
While working within the app as well all the operations are very slow (not much but a 2 second delay on most of the things is visible).
I have 3 browsers installed on my PC
IE 11 running Flash version 23.0.0.207
Chrome 55.0.2883.87 running Flash version 24.0.0.194
Waterfox 32.0 also running the same Flash version as IE 23.0.0.207
Running the app from all 3 these browsers is slow apart from Waterfox.
I deleted all the caches from the flash settings in control panel and for chrome I used the web interface (http://www.macromedia.com/support/documentation/en/flashplayer/help/settings_manager07.html).
I cleared all browser caches. We are running McCafee which I disabled.
I had a look at any windows updates that was done recently which I uninstalled.
What could be different between these? What else can be checked to see what is making this app slow in IE and Chrome?
The slowness could be caused by the files not being cached by the browser like they used to be. I would start there. If you reload the page and you're not seeing a 304 "Not Modified" for the swf(s) you're loading them from the server each time where they used to be loaded from the browsers cache.
Here's some more info on the subject: https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/http-caching
Both Chrome and IE have developer tools you can load to see the http calls and check the headers and response codes.
https://msdn.microsoft.com/en-us/library/dd565628(v=vs.85).aspx
https://developer.chrome.com/devtools
I am working on WebStorm and Chrome. It allows me to live coding.
I would like to change Chrome to Firefox, because it has not got problems with set mobile view.
So, how can I set live coding with WebStorm and Firefox?
I want to write code and see changes on screen without saving. Any tips?
Live Edit in FireFox is not currently supported, please vote for WEB-1805.
WebStorm doesn't provide integration with available third-party solutions, but you can still use Browsersync, etc. - start it in terminal or using Gulp/Grunt file, open your application URL in FireFox, hit Save All in WebStorm to get edited files saved - page will be updated
I built a chrome extension that opens certain site instances in new tabs using window.open(url, '_blank');
It seems to work a little slow on development but very slow on production.
I tried to open the chrome app using --process-per-tab and --process-per-site, according to the chrome's article: https://www.chromium.org/developers/design-documents/process-models#1_Process_per_Site_Instance
But nothing seems to work. I noticed the first time I opened the chrome with the beginning url then it looks fast.