I am looking for a list of browsers that support HTTP Push.
I've looked around and I cannot find that list.
I know that Firefox, Webkit, Opera support it... But what about IE?
Also what version of those browsers support it?
As for Socket.io library, supported browsers are listed here. If you are interested in Websocket support, take a look at this article.
Related
I recently developed a cross-browser extension using crossrider.com, it seemed like a reasonable choice of "framework" with multiple recommendations in blogs, etc.
The trouble is crossrider also run an ad network and it seems they're sending browser meta data to that network from all their browser plugins. Sophos are blocking their use (although it is possible to add an exception). Chrome is now also blocking the installation of staging versions of your extension during development.
I would love to hear from crossrider but haven't had a reply to my emails.
So my question is can anyone recommend an alternative framework for cross-browser extension development.
You can try Kango (kangoextensions.com) but beware, theres not alot of help available. That being said, its a fairly simple framework that works for Chrome, Firefox, Safari, and Opera. They used to offer IE support for a fee but they seem to have stopped that now.
I am developing a cross browser plugin for document viewing (.pdf, .doc, .xls, .mht, .tiff, .dwg). It needs to be a plugin and not the extension. Whatever i try to search takes me to the links for extensions and not for plugins. I found NPAPI as cross platform plugin architecture but soon found out that major browsers have planned to depreciate and stop the development support, Chrome is one of them. I have been searching from last 3 days and finding myself in no man's land.
I intend to develop the tool as a business requirement and not use some already developed software tools like quickview. Please provide some good links to the cross browser plugin development. A little help will mean a lot. Thank you
The only truly cross-browser technology, supported by all the major browsers, are standardized or standards-track web technologies. If you want something that works in all browsers, you'll need to develop using the technologies that browsers are designed and intended to support.
The reason you aren't finding any resources for doing what you describe is that there's no way to do it.
I have tried and tested various approaches to make webRTC work on internet explorer
using Google chrome plugin
webRTC4all
Sipml5 is not responding to either of these approaches
I also read the "Customizable, Ubiquitous Real Time Communication over the Web (CU-RTC-Web)
Real-Time Media and Peer-to-Peer Transport API " document which is still in development stage and not version is released .
Could someone tell me a solution to the problem , or correct me if i am wrong .
WebRTC is supported now in Chrome Stable and Firefox Beta, and in Internet Explorer via Chrome Frame: see my blog post, which has a screencast video showing this in action. Support in Opera mobile and desktop is planned.
Okay i am going to answer my own question here .. after months of wait , IE has decided to make Sype like WebRTC ( plugin free ) http://venturebeat.com/2014/10/27/microsoft-eyes-webrtc-for-plugin-free-skype-calls-in-internet-explorer/. however no details / confirmation available up-till now
What, if any, support is there for CSS3 in mobile browsers? The specific browsers I'm curious about are the ones used in the iPhone, Android, and Blackberry phones. Any links to relevant resources would also be greatly appreciated.
Both iPhone and Android systems use WebKit as the rendering engine in their mobile browsers. I believe Blackberry are moving to Webkit as well at some point. This engine has some of the best support for parts of CSS 3 available at the moment, as well as quite a lot of proprietary extensions.
I would recommend researching what is available in WebKit, and then testing.
A great resource for support tables is http://www.quirksmode.org where PPK is doing more and more mobile browser testing to answer just these kind of questions.
You can try acid3.acidtests.org and http://www.css3.info/selectors-test/test.html on the respective browsers to check some compatibility, but that may not be an exact determining factor of full compatibility. However I don't think any of the mobile browsers currently fully support CSS3.
a do quirksmode.org specifically this page: http://www.quirksmode.org/webkit.html
In the BlackBerry Documentation for Developers, there is a documentation for the BlackBerry Browser, including CSS Reference - BlackBerry Browser. There is no specific mention of CSS3, but that document lists supported CSS properties.
There is also a BlackBerry Widget web standards support page that states 4.7.1 and 5.0 have partial support for CSS 3 color and full support for CSS 3 marquee, CSS 3 media queries, CSS 3 namespaces and CSS 3 selectors.
well when i mind internet i found usefull source to you i hope it will help you more excellent description on mobile browser compatablity
Most smartphones use modern browser engines that have implementing HTML 5 (or at least partially). Should I start using HTML 5 for my web application ? Where can I find a list of browser engines used by most popular devices (iPhone,Android,etc.) ? My application doesn't have to work on older desktop browsers.
Depending on how commercial/critical your web page is, the answer differs.
If it is CRITICAL that it works on ALL smart-phones, use HTML4, with a view to upgrading it to HTML5.
If it is preferable that it works on most smart-phones HTML5 will be fine. Even where it is not supported, the page will render - it just won't look like you intend. I'm using HTML5 with a couple of additions that help older browsers to render it correctly.
I did a browser test of HTML 5 (with the helpers for older browsers) with the following results:
http://www.stevefenton.co.uk/Content/Blog/Date/200907/Blog/HTML-5-Browser-Test/
According to this post (iPhone developers abandoning app model for HTML5?), it seems that starting to use HTML 5 is feasible.
Unless you only cares iphone, 5 is not well supported for "most" smartphones.
If you really want good compatibility on smartphones, you'd better keep with 4.
The Wikipedia mobile browsers page has a decent table at the moment.
On the “most popular devices” issue, if you’ve got any information about phones used by your app’s intended audience, that’ll be more valuable than general popularity.
Having said that, I think in general the iPhone’s sales figures are significantly ahead of everyone else, and the iPhone has great HTML5 support. I’d go ahead with HTML5, as I think the other smartphones will either catch up with their HTML5 support, or disappear.
Android’s pretty much the only other smartphone with significant sales, right? I think Google’s keen on HTML5.