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.
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.
Hey i was wondering if anyone else has had problems with css 3d running on chrome on linux (specifically fedora 17). Chrome in Windows seems to handle everything fine but for some reason it won't work in Fedora. I get errors saying that my browser doesn't support 3d transforms.
Chrome/ium is probably the most popular option, so if the version you tried wasn't working, you may want to update to the very latest -- something like the Chromium Daily Builds. If even that is too buggy to work with, you might want to try a different Webkit browser for Linux.
Midori and Epiphany are two decent options. As an added bonus, I think both of these browsers will use the version of Webkit that you have installed on your system (unlike Chrome, which comes with its own version of Webkit). That means that you should be able to build Webkit from the latest nightly source release, and Midori or Epiphany will automatically use that version.
WebKit Nightly Builds
I hope that this help you.
The original browser doesn't support css3 and HTML5,It even cannot display jQuery Mobile demo and Ckeditor.Is there any replacement for this?
There's an update (codename Mango) on the way to bring IE9 and its new Javascript compiler to Windows Phone 7. IE9 is an implementation of HTML5/CSS3. I have not special knowledge but the rumors on the web:
http://gizmodo.com/5724937/windows-phone-7-rumored-updates-copy--paste-ie9-html5-and-silverlight-coming
wp7 still runs IE7 which was made when HTML5 and CSS3 were not even though about!.
You could check out Opera Mobile as of now.
for jQuery mobile demo, you could refer browser support here: http://jquerymobile.com/gbs/
cheers
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