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.
Related
I have created an Opera extension, but have a question about the "manifest.json" file.
Specifically, I'm not sure what version I should put in "minimum_opera_version".
According to the documentation (which all points to the chrome developer API), based on the API calls I make the minimum version is Chrome 26.
However what version of Opera is that? How can I figure out what minimum version of Opera the extension requires?
Opera stable is now at version 49. First ChrOpera was ver 15. It's mainly those on XP that might need to resort to a much older build than current. You don't need to state minimum_version at all in the manifest.
The minimum_opera_version usually depends on the APIs you use in your addon. For example if you use Alarm API in your add-on then check from which version of Opera does the support for Alarms API exists and configure accordingly.
-> https://dev.opera.com/extensions/apis/
I have just upgraded myself to new version and started development in 9.0.1 Revision 20131022.0932 ( release 9.0.1). I have couple of small queries.
1) Am I using the right version for development or need to upgrade by implementing patches etc?. This is stable for development?
2) Previously I was developing applications on 8.5.2 but my clients were on 8.5.x and 9.x.
This migration is safe for existing applications? no crashes? no code mismatch? Is their any guideline for developer? Co-Existence of clients is possible?
Please guide me and thanks in advance
Best Regards,
Qaiser
In general, upgrading to the latest Designer version is ideal, especially with (as Per recommends) the latest fix packs, as well as on the server.
For non-XPage design elements, there should be no incompatibilities with 8.5.x through 9.0.1, so you're good there.
If you do XPages intended to be rendered by older versions (either older servers or XPiNC in older clients), you could run into trouble there, using properties and controls that don't exist there. You can mitigate that a bit by going to the app's "Xsp Properties" in Designer and changing the "Minimum Supported Release". That won't help you avoid trouble with third-party plugins not installed everywhere, but it helps with the core runtime controls.
Our current production version is PC 11.52 patch1 and our company is going to start IE11 roll out soon. We don't have many issues with our current production version so we would like to use it. But 11.52 doesn't support IE11. Because full migration needs lots of work (we have more than 100 projects), we are investigating alternative solutions. We tested 11.52 Vugen with IE11 and it seems, that Vugen can record scripts in WinInet mode. Would it be possible to record scripts using WinInet level capture and run them using Sockets? Is there some limitations using WinInet capturing and what pitfalls this approach might bring?
I don't know about PC 11.52 but I can answer regarding LoadRunner 11.52 (VuGen 11.52) It doesn't support IE11 because in IE11 Microsoft added some API which we had to add to the LoadRunner in order for it to work. The API was officially added in version 12 but a patch exists for version 11.52. The problem is that the patch is not available for direct download so you will have to open a support case. When you open the case please describe the problem and ask the patch for defect (77102).
EDIT: If you ask the same question on the official LoadRunner support forum then the support staff will be able to attach the file directly.
I'm looking for the way to conduct cross-browser compatibility test on my ubuntu. Firefox and opera don't cause problems, but I didn't find any guide how to install older versions of chrome. Do you know how to check my code in this browser on my computer?
You can take screenshots in different versions in Browserstack. Also you can browse there using different browsers, but you will need to pay for that.
In general, there is no need to test compatibility against anything but the latest version of Chrome, since Chrome updates itself automatically. Just expect that anyone using Chrome to view your site will have the latest version.
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