chrome dev tool debugging browser version - google-chrome

Can i change the version of browser while debugging.
I'm currently using chrome.
I want to test my application for chrome older version compatibility.
Is their any option using chrome dev tools to change chrome versions.

You can use Browser stack for the same it free for some time
browserstack

There's definitely no feature within Chrome DevTools to change Chrome versions.
Chrome doesn't provide a simple or official way to download old versions. You might be able to find some unofficial archives of old versions, but use with caution.
Can I roll back Google Chrome to a previous version?
No - rollback is not supported.
To get to a previous version (which would not be supported by Google),
you would need to uninstall your current version, delete every user's
saved profile data, and re-install the older version. Users' personal
profile data is kept in:
On Windows XP: C:\Documents and Settings\\Local
Settings\Application Data\Google\Chrome\User Data On Windows Vista /
7: C:\Users\\AppData\Local\Google\Chrome\User Data
https://www.chromium.org/administrators/frequently-asked-questions

Related

Emulate an older version of chrome within the dev tools

I need to emulate an older version of chrome. I want to avoid the solution where I have to uninstall the current version and install the desired one each time I need to test my app. I came across this article but it doesn't quite answer my question. Thank you!
It's not possible to emulate older versions of Chrome from within DevTools, as is possible in IE. It's not very reliable to emulate them anyway. I've used IE 8 emulator in the past, and on occasion it has provided different results from the version I installed on an XP VM.
In theory, it should be possible to install multiple Chrome instances side-by-side because the installation directory is OS user based. However, I don't think the installations are fully isolated from one another. At least in Windows, the application would likely write to the same registry keys. In OSX, you might be alright, provided you modify the user directory path.
An alternative solution would be trying the portable versions of Chrome that appear over the Internet, usually illegally. Everything is self contained in a directory, but it will likely perform differently from normal installations. Check out PortableApps.
I think the best solution would be to set up some VMs for the different environments and browsers you want to test with. You can manually set up these, using VirtualBox or similar. Many hosted providers will allow you to spin up fresh VMs with automated tasks to install applications and services. You have to pay for these though.
If you just need to check what server returns for old browsers (not full emulation), you can set User-Agent in Network Conditions (for now, chrome 67).
Just for completeness, here is a link (September 2021) that provides historical snapshots of the 'chromium' browser, sorted per operating system and per 'position'. I needed this when I had to test on an 8-year old version of Chrome(~ium)
https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html
The URL looks legit (googleapis.com) to me, but please check for yourself before downloading. At your own risk.
Updated on 21/03/2019
I have found the following link which contains links to previous Google Chrome Versions (32bit, 64bit and Linux).
https://www.slimjet.com/chrome/google-chrome-old-version.php
Old post
Just found out that different versions of Google Chrome can be installed.
You will have to uninstall your existing version.
Download the package from here - https://www.chromium.org/getting-involved/dev-channel
Follow the instructions and install.
Hope this helps someone. The downside is you have to uninstall your current version.
Cheers!
Today you can run Windows Sandbox to avoid installing malicious programs. (Windows Professional or Enterprise Edition is required).
more info:
Windows Sandbox Doc
While I don't have a way to emulate a different version, I did find a way to have a current and an old version installed at the same time. For the 'current' version I installed Chrome Beta. Then I set the regular version of Chrome to the older version I needed.
Google's docs didn't put all the information in one place, so here are the steps for a normal Chrome user in Windows 10:
Download the Google Update policy template (alternatively Chrome Enterprise also contains the files you'll need) and unzip it.
Copy the .admx and .adml files into %systemroot%/PolicyDefinitions (.admx files go there and .adml in the language subfolder (en-US) as found in the zip you downloaded)
Open Group Policy editor and the required settings now exist
In Computer Configuration->Administrative Templates->Google->Google Update->Applications->Google Chrome,
set Rollback to target version to enabled
set the Target version prefix override to enabled and your desired version
(e.g. 86. for version 86)
Finally open Chrome, go to Settings->About and let it check for updates. Chrome will automatically download the target version and prompt you to restart.
Do note that this deletes local user profiles and recreates them from remote including redownloading browser extensions, so use with caution. Remember to go back to the normal version of Chrome by unsetting the Group Policy settings and letting Chrome update itself when you're done.

Which version of Chrome am I using?

How do I know which version of Google Chrome I'm using on Windows? I installed Chrome for work from:
https://www.google.ca/work/chrome/browser/
But the version number is exactly the same as the normal one. What is different that can prove I'm using the enterprise version of Chrome from the above URL?
Or just do this:
chrome://version

Why can't Windows XP handle newer SSL certificate versions?

As I understand, as Windows XP support was officially dropped, the newest versions of SSL certificates used in certain websites cannot be accessed by Chrome and IE on WinXP due to incompatibility. However, Firefox apparently still does support Windows XP and can access those websites freely.
I don't quite understand how the SSL certificates compatibility works, how is it possible that on Chrome and IE it requires you to switch to a new OS altogether but that's not needed when just using a different browser? Why can't a simple community developer just create a "patch" for Chrome and IE if Firefox can support them? What's the connection between the browser and the OS? Where do I draw the line?
OK, so looking at the example of mpql.net, we start with the SSL Labs analysis.
The problem appears to be that the server only supports elliptic curve cryptography (the various TLS_ECDHE_xxx suites) and, according to the MSDN articles Secure Sockets Layer Protocol and TLS Cipher Suites, Windows XP doesn't include any of the elliptic curve protocols. This is not related to the certificates per se, but to the way the web server is configured.
Firefox still works because it uses its own cryptographic library rather than using the SSL support built into Windows. Of course, if you were using a version of Firefox as old as Windows XP is, it probably wouldn't work either. :-)
Solution for this problem in XP is installing KB3055973-v3 that adds support for TLS 128-bit & 256-bit Advanced Encryption Standard (AES) cipher suites.
Google for this solution and beware it is natively for English OS version, otherwise you need to modify the installation files.
Note that I installed "Windows Embedded POSReady 2009" before.
certain websites cannot be accessed by Chrome and IE on WinXP due to incompatibility. However, Firefox apparently still does support Windows XP and can access those websites freely.
Chrome and IE use the CA store of windows while Firefox uses it's own independent store.
Why can't a simple community developer just create a "patch" for Chrome and IE if Firefox can support them?
It might be that some developer can do it, but why should somebody invest its time to support an OS which is dead and insecure just to support browsers which are no longer supported (Chrome will drop support end of 2015). If you feel this needs to be done anyway just do it. Otherwise, drop XP or at least use Firefox with it.
Although I cant say im 100% correct I believe ssl has everything to do with the browser and not much to do with the actual operating system. So I ran into an issue where the very opposite from what you are asking. A client was on a windows 7 machine and needed to access time warner business email through chrome but couldn't because of a SSL issue. The problem was that Chrome dropped support for the older version of SSL and so her options where use IE or Firefox or downgrade and hope chrome doesn't force its self to update. Microsoft is wanting users to upgrade so of course they are not going to keep IE up to date and google isn't going to support an outdated operating system. Firefox is open source so it makes sense that people would keep the browser compatible with as many devices as possible. Hope this helps.

Making chrome extensions on chromium vs. chrome

Pretty simple question-- is it possible to create google chrome extensions via Chromium, and have that same extension be used with people running Chrome on different OS's?
I'm developing on Ubuntu.
Yes, it's perfectly possible; however, Chromium included in Ubuntu will probably seriously lag behind main Chrome versions.
You won't benefit from new APIs available to Chrome users, as well as be unable to test the extension for the majority of users.
Your best bet is, indeed, to install Chrome from Google's repositories.

How to troubleshoot Google Chrome Sync issues?

I am using custom sync options to synchronize only some of the artifacts from a Google chrome installation - just Bookmarks, Extensions and Open Tabs. All three are working on well on my two windows computers - but on the Linux machine, I am not getting the extensions. I have tried wiping the Linux Chrome data (by removing ~/.config/google-chrome/ and re-configuring it, the the problem remains the same.
I am wondering if there are any logs that the chrome browser produces that can give me a hint on what the problem might be.
Thanks a lot
Looks like this is not a bug but a "feature", different support of extension per OS, but seems there might be hope this is fixed in future releases see:
Chrome Web Store to get multi-platform app support for Windows, Mac, Linux, Android, iOS, and Chrome OS
Other Deployment Options