I am testing my web application in Safari 5.1.7 on Windows (the latest version available). It shows a specific bug which I want to verify in Chrome that is using the same version of Webkit as Safari 5.1.7. How can I find out which Chrome version I need to download?
From Wikipedia page about Safari versions I know that Safari version 5.1.7 uses Webkit in version 534.57.2, but I can't seem to be able to translate that version to the corresponding Chrome version.
I found this post: Which version of Webkit in a given Chrome release?, but it doesn't quite help because it only gives the version of Webkit in a given Chrome release, not the version of Chrome that contains a given Webkit version.
What I usually do in this case is look at this list of chrome user agents and match to the closest webkit version, but it's tricky because you'll never get a full match.
For the sake of your specific questions, to get close to Safari 5.1.7's webkit engine you'd want to get a copy of the last Chrome 12 version. Technically Webkit 534.57.2 is somewhere between Chrome 13.0.766.0 and Chrome 13.0.782.1. But given that it's already hard to find old copies of Chrome. Finding an old very specific version like that on the web is near impossible.
Another great reference to find equivalent browser versions by date is the caniuse date relative data.
Look up any feature (such as 'flexbox') and click on "Date Relative" for a visual comparison of all browser versions by date releases.
Related
Chrome and Firefox have supported AVIF images for some time now, and it is my understanding that Edge is based on Chromium, which caused me to assume that it too would support AVIF images.
However, I just tested an AVIF dependent application in Edge Version 110.0.1587.46, in Windows 10, and none of the AVIF images are being displayed.
I stopped using Internet Explorer due to its slow implementation of modern web standards (many years ago). Today, I give Edge a chance to redeem "the company that provides it", and it appears that even though it is based on Chromium, the offering still fails to implement modern web standards.
Why aren't AVIF images supported in Edge, given that Edge is based on a browser that does indeed support AVIF images?
As of October 2021, the AVIF image file format support was introduced in Google Chrome 85 and Firefox 93 versions. If your browser is currently on a newer version than one of these it also will be supported. Microsoft Edge isn’t currently supported, but since the new Microsoft Edge uses the same Chromium Engine it won’t be long until support is rolled out. However, there is an AV1 Extension add-on available to download on the Microsoft Store (https://apps.microsoft.com/store/detail/av1-video-extension/9MVZQVXJBQ9V?hl=en-us&gl=us&activetab=pivot%3Aoverviewtab). This provides support on Windows 10 devices and Edge if installed.
PS:
In Edge Canary 112, Microsoft is testing adding support for the AV1 Image File Format (AVIF) in the browser.
Command-line flag: --enable-features=msEdgeAVIF
Just to answer your question regarding Windows 11 Edge. Edge has the same "latest version" on both Windows 10 and Windows 11. However, .avif pics are also not supported on Windows 11 Edge.
The lack of support for .avif in Edge is by design, out of compatibility concerns or something. AV1 Video Extension from Microsoft Store is used to enable you to view .avif pics on Microsoft Photos App, but won't affect Edge.
Good news is, as #D A has said, the Dev Team is testing to add support for .avif in Edge Canary.
This can be a most common question. But no any clue about browser versions. More over, Angular site itself says as following.
What browsers does Angular work with?
We run our extensive test suite against the following browsers: the latest versions of Chrome, Firefox, Safari, and Safari for iOS, as well as Internet Explorer versions 9-11. See Internet Explorer Compatibility for more details on supporting legacy IE browsers.
If a browser is untested, it doesn't mean it won't work. You can also expect browsers to work that share a large part of their codebase with a browser we test, such as Opera 15 or newer (uses the Blink engine), or the various Firefox derivatives.
— AngularJS FAQ - What browsers does AngularJS work with?
However, there is no any note which versions are supported. I googled, but couldn't find. Any one let me know what browsers and their versions do support which version of angular ?
Browser support of AngularJS:
Internet Explorer: 9+
Versions 1.2 and later of AngularJS do not support Internet Explorer versions 6 or 7.
Versions 1.3 and later of AngularJS dropped support for Internet Explorer 8.
Opera 15+
Firefox, Safari, and Google Chrome
As mentioned in a StackOverflow Question here: Which versions of firefox does angularjs support?, since they say which IE version they support and not Chrome, Safari, or Firefox, it's safe to assume all the versions are working.
Version Support Status
Any version branch not shown in the following table (e.g. 1.6.x) is no longer being developed.
Version Status Comments
1.2.x Long Term Support Last version to provide IE 8 support
1.7.x Long Term Support See Long Term Support section below.
Long Term Support
At this time we will focus exclusively on providing fixes to bugs that satisfy at least one of the following criteria:
A security flaw is detected in the 1.7.x branch of the framework
One of the major browsers releases a version that will cause current production applications using AngularJS 1.7.x to stop working
The jQuery library releases a version that will cause current production applications using AngularJS 1.7.x to stop working.
— AngularJS Documentation - Version Support Status
According to AngularJS document：Internet Explorer Compatibility, the answer should be IE 9。
AngularJS 1.3 has dropped support for IE8. Read more about it on our blog. AngularJS 1.2 will continue to support IE8, but the core team does not plan to spend time addressing issues specific to IE8 or earlier.
The project currently supports and will attempt to fix bugs for IE9 and above. The continuous integration server runs all the tests against IE9, IE10, and IE11.
I used the BrowserWindow.CurrentBrowser feature in order to run my Coded UI test cross over different browsers. However it is failing.
I uninstalled the latest versions of FireFox (26) and Chrome (32.0.1700.76) and re-install older versions and it is working again.
Do you have any idea why cross browser of the Coded UI doesn't work with the latest versions of FireFox and Chrome?
How can I fix the issue (except installing an older version)? Is there any work around?
Thx
This article explains cross browser testing with COdedUI http://msdn.microsoft.com/en-us/library/jj835758.aspx
Specifically "Install the Selenium components for Coded UI Cross Browser Testing Visual Studio extension."
Which can be found here: http://visualstudiogallery.msdn.microsoft.com/11cfc881-f8c9-4f96-b303-a2780156628d
Or you can search for them with nuget inside visual studio
Note: Selenium does not support the lastest versions of firefox and chrome
"
Supported Browser versions
The following versions of browsers have been verified and are supported:
Firefox 23.
Latest version of Chrome (version 29.0.1547.59 m as of 9/4/2013)
"
I found only FF 24.0 version work for me.
The latest version does not.
For chrome, the latest version also works.
I'm talking about the ability to provide a regular expression as the "pattern" attribute for an HTML textfield input. Like:
<input type="text" pattern="[abc]{3}"/>
According to http://www.chromium.org/developers/web-platform-status/forms, Chrome has supported this attribute for a while (not listed under any specific milestone). But according to http://www.coreservlets.com/html5-tutorial/input-types.html, this user tested the feature in Chrome 8 and it didn't work despite the official site claiming it should.
This feature seems to work fine in my version of Chrome, which is the latest version. However, I can't seem to find out which versions of Chrome this feature is supported in. The application I am working on is required to support Chrome versions as low as 6.0. So I wonder if someone can help me by letting me know what version of Chrome this feature was introduced?
PS: This feature definitely does not work in Safari at all. It's odd that it works in Chrome and not Safari as both are based on Webkit. This is even more evidence to me that it was probably only introduced in a fairly recent Chrome version.
It looks like has might have been supported since version 10.0.
I knew that as of some release of Chrome 9 that rounded corners now listen to border-radius.
I got curious and tried it on some other browser/OS combinations and found that the following webkit browsers support the non vendor border-radius.
Chrome 9.0.597.98 on windows 7
Chrome 9.0.597.102 mac osx (snow leopard)
Safari 5.0.3 on windows 7
Safari 5.0.3 on mac osx (snow leopard)
With Chrome's automatic background updating in place it's rare for users to be running older versions unless specifically required.
So my question is, is it finally safe to drop the -webkit vendor prefix for css3 border-radius ?
Yes, I believe it's safe to drop it.
See: https://developer.mozilla.org/en/css/-moz-border-radius
Lowest version for unprefixed "border-radius"
Safari | Chrome | WebKit
5.0 | 4.0 | 532.5
So, it's safe to drop if you don't care about users running older versions of Safari/Chrome.
Not many users are running old versions of Safari/Chrome - these browsers aren't IE, where older versions are sometimes clung to for aeons.
Users running these browsers are often savvy enough to update, and both Safari and Chrome aggressively try to update themselves (Chrome even does it automatically).
Also, http://css3generator.com/ has dropped it. (the top Google result for "css3 generator")
I second Rafal's opinion. Especially iOS 3.x devices should still be around a lot. So it can't harm to give them the -webkit- prefix. Also http://css3please.com/ (the other css3 generator) still includes it ;-)
Mobile version of the browser usually are not as up to date as desktop. So it depends who is your audience
iOS 4 still need webkit vendor prefix on border-radius
See here http://caniuse.com/#border-radius