YUI 2.9 with new versions of browsers - browser

We have developed a framework using YUI 2.9. As the newer versions of browser are released for like a month eg FF. We have to do testing for all the component with newer version. Is there any way this testing can be compromised? YUI 2.9 will be compatible with new browsers?

You shouldn't develop new software with YUI 2. It isn't supported anymore by Yahoo! or the community. YUI 3 sometimes breaks with new browsers and it needs to be fixed, so there's a good chance of YUI 2 breaking.

Related

JSF1.2 and RichFaces 3.2.1 upgrade

I have the project which is designed and developed on very legacy frameworks. The frameworks which we are currently using are:
jboss-seam-2.2.1.jar
jsf-api-1.2_04-p02.jar
jsf-facelets-1.1.14.jar
jsf-impl-1.2_04-p02.jar
richfaces-impl-3.2.1.GA.jar
These are quite old frameworks, may be around 12 years old or more.
Now, we are planning to upgrade these version to the latest stable version of the frameworks.
The question is, can we directly move from jsf1.2 to jsf 2.3 ? I don't see any documentation or reference for this migration.
Along with JSF upgrade what all are the components we may need to upgrade? Any Direction ?
Thanks in advance!!!

How to decide the minimum browser version my website should support?

As a front-end developer, how should I realize what is the minimum version of Firefox, Chrome, Safari, and etc that my web app should support? Should I consider all the users would use the last stable version? If not, how many older versions should be considered?
P.S. I faced this question wen I decided to use CSS grid display and my colleagues believed some users' browsers may not be updated to support this feature.

Which browser versions can run Flash 11.7?

Subject says it all. What are the oldest browser versions that can run Flash 11.7?
These are the versions I need to support for historical reasons, even though I am running HTML5.
All I can add is that most browsers that support NPAPI or ActiveX will run Flash Player 11.7, if that's the browser-installed Flash Player plugin version.
(1) You can check NPAPI support at the Wikipedia entry :
Chrome : supported up to version 41 (PC/Mac) | version 34 (Linux)
Firefox : supported until March 2017.
IE : should work up to IE 11 (if not higher, but I've not tested). note: uses ActiveX for plugins.
(2) Flash Player was widely released by June 2013.
Hopefully, installing a browser version from around that date should help you run the content.

which browsers are supported by Selenium 2.0

So, now I am looking for a list of all the browsers and their versions which are supported by Selenium 2.0
I searched http://docs.seleniumhq.org/about/platforms.jsp also but it seems the document is not updated, as I cannot see FF later versions like 13 and 14 listed over there.
So far, I have just worked on FF 13, 14 and IE 8
Could someone suggest me any link or a list here the browsers with their versions?
Many thanks for any help!
Regards,
The officially supported browser versions are as follows:
IE: Versions 6-10 supported. Version 11 should work fine, but is untested. IE6 support is to be discontinued on 15 April 2014.
Firefox: Versions supported using native events are the current version, immediately previous version, current extended support release (ESR) version and immediately previous ESR release, as determined from the date of release of the Selenium components. The last public Selenium release at the time of this writing was on 27 August 2013, and at the time, that means the supported Firefox versions were 23 (current), 22 (previous), 17 (current ESR), and 10 (previous ESR). This is complicated by the fact that this version support is only applies to so-called "native events"; if you don't use native events, a much wider range of Firefox versions is supported.
Chrome: Version support is determined by the chromedriver exectuable used, and is available at the chromedriver download site, but is usually stated as the current and previous stable channel releases, the current beta channel release, and the current dev channel release, as determined by the date of release of the chromedriver executable.
Opera: The OperaDriver supports Opera 12.x. It is theoretically possible to use the chromedriver executable for Opera 15+, but Opera Software has yet to make the necessary changes in Opera to allow this.
which browsers are supported by Selenium 2.0.
Mind you, that Selenium 2 relies on on the drivers for each browser. What you should turn to, is the versions of IEDriver, ChromeDriver, FirefoxDriver, etc.
Each WebDriver supports a range of versions of the browser.
For example, chromedriver 2.2 works on Chrome v27-29 I believe. As far as a list goes, I think you'll have to dig. There aren't any sources i've found yet.
The Firefox driver is native to the main jar as a firefox extension so that's not as obvious but IE and ChromeDriver supported versions can be found on the driver download page. You can see on the page below that the latest chrome driver supports version 28-31. One thing you'll probably notice is that every time a new FF version comes out, typically less than a month later a new selenium jar will come out.
https://code.google.com/p/chromedriver/downloads/list
ChromeDriver server for win32 (v2.3.220795) supports Chrome v28-31

Cross-Browser Extensions API?

There are tools for developing cross-platform browser plugins.
Are there any similar tools or APIs for browser extensions (i.e. toolbars, or filter systems like AdBlock)?
Yes, but unfortunately each one has significant drawbacks.
Kynetx supports IE, Firefox, Safari, and Chrome, but extensions are dependent on the Kynetx extension to work. In addition, Kynetx apps are built using an odd, proprietary Kynetx Rules Language. There is no cost to use the Kynetx platform. UPDATE: Kynetx has shut down
WebMynd supports IE, Firefox, Safari, Chrome, and is in private beta. From what I have been able to determine, WebMynd is a very small San Francisco-based startup that is still getting off the ground. Their library is standalone and provides a Javascript API, and they use a monthly billing model. UPDATE: company pivoted, now for mobile, trigger.io
Crossrider supports IE, Firefox, Chrome and Safari. Recently out of beta (as of June 2012), Crossrider is free and offers a jQuery-based development experience. Publishing methods for your extensions include an embeddable website widget, download links, and a customized windows installer. However, CrossRider does not allow you to self-host your plugin files. UPDATE: As of 27.09.2016, CrossRider is terminated and it will be available only until 27.10.2016.
KangoExtensions supports IE, Firefox, Chrome, Safari, Opera. Seems very new and bleeding edge, like Crossrider, also looks promising. UPDATE: No updates in over two years.
IE and Firefox seem to be the hardest to develop for, although Mozilla JetPack aims to greatly simplify Firefox extension development.
There is also very young framework for cross-browser development called BabelExt, from the author of Reddit Enhancement Suite. I like that it builds restartless Jetpacks for Firefox.
See more on github, https://github.com/honestbleeps/BabelExt
Mozilla has recently introduced WebExtensions API. For now it's actually almost a copy of Chrome Extension API (but some APIs aren't implemented yet). It has been introduced just a few days ago so it still has a lot of problems and unsupported APIs. But if you're interested in writing extensions for Chrome, Opera and Firefox you should pay attention to the state of WebExtensions API.
UPD 27.10.16. There is a page Are-we-WebExtensions-Yet which summarises the current state of WebExtensions. By their current estimate 44.99% extensions from Chrome store should work in Firefox.
ExtensionMaker is another one project related to cross browser extensions development. It is not a real framework. It is kinda IDE that allows you to design basic extensions.
Of course, it is not suitable for a serious projects. But I like the idea.
Full featured version is available for free. There is just small limitations on the way of using generated extensions.
Yes, the browser extensions development company has a framework-one code for all browser views

Resources