I'm running Firefox 7 in Ubuntu 11.04, and I noticed socket.io was falling back from web sockets to xhr-polling, so I typed WebSocket in Firefox's console, and got
[00:48:21.224] ReferenceError: WebSocket is not defined
On Google Chrome 14 I got
WebSocket
function WebSocket() { [native code] }
According to this, WebSockets is partly supported since firefox 4 and fully supported since firefox 6.
Is it only different in firefox on linux ?
In Firefox 4/5, WebSockets support is present but disabled (activated via about:config). In Firefox 6, Mozilla enabled WebSockets by default but added the "Moz" prefix. Also, note that Firefox 6 uses the newer HyBi protocol and W3C API. Chrome added the HyBi protocol in Chrome 14 although Chrome has never used a prefix.
The protocol is effectively complete and the official first version is expected to be published in about 6 weeks (the wire format has not changed significantly in months). The API has also been quite stable for months and Chrome 14+ and Firefox 6+ basically have the same implementation of the API. For some reason Mozilla has chosen to be even more cautious than normal with WebSockets prefixing. Perhaps it is a reaction to Google not being careful enough about prefixing unstable APIs.
Unless you are interested in binary message support, specific error and close condition handling or sub-protocol selection, then the WebSockets API has been essentially the same since Chrome introduced it a couple of years ago. If you are implementing a WebSockets server then you will need to know about the various versions of the protocol which has seen significant changes in the past 2 years.
Try MozWebSocket instead.
https://developer.mozilla.org/en/WebSockets#AutoCompatibilityTable
Firefox 7 supports hybi-10 "straight out of the box." I've been running it against my Firefox 7 supports hybi-10 "straight out of the box." I've been running it against my websocket server. You can try my online demo with Firefox 7 and let me know if you have any problem. I've tested it from Ubuntu 11. I have that set up right now.
Related
I'm using sap gui in macbook os x. Whenever I execute the web dynpro programs, the browser will be opened and is keep on loading and it never ends. How can I fix this issue?
Though your Safari version seems actual, I assume your MacOS version is not supported by SAP, as PAM lists only versions from 10.11.
SAP issues PAM (Product Availability Matrix) sheets where you can match your Browser, Platform and Product versions and check for inconsistencies. Netweaver 7.4 PAM can be found here.
Probably, your MacOS version is too old for SAP and you should try to update. However, personally I feel that problem lies elsewhere and you should ask for help of experienced BASIS. Maybe your WDA uses certain feature that is not supported by Safari or WDA in general.
Additionally you can check:
Note 1634749 concerning Safari support for Web Dynpro ABAP (version for non-S-users).
Note 1098009 for general Web Dynpro ABAP browser limitations
Browser supporting page from SAP.
There is library Resumable.js that is:
a JavaScript library providing multiple simultaneous, stable and resumable uploads via the HTML5 File API. The library is designed to introduce fault-tolerance into the upload of large files through HTTP.
but according to Resumable.js site:
Resumable.js does not have any external dependencies other the HTML5 File API. This is relied on for the ability to chunk files into smaller pieces. Currently, this means that support is limited to Firefox 4+ and Chrome 11+
Sometimes developers do not immediately update documentation. Are there any changes at the moment: does Resumable.js support resumable uploading for IE v11 and Windows 10 Edge?
According to their current documentation, they support all major browsers, including Internet Explorer 10+ (Github Resumable.js):
Resumable.js does not have any external dependencies other than the
HTML5 File API. This is relied on for the ability to chunk files into
smaller pieces. Currently, this means that support is widely available
in to Firefox 4+, Chrome 11+, Safari 6+ and Internet Explorer 10+.
Their documentation doesn't say anything about Opera, but it mentions that the only Resumable.js dependency is the HTML5 File API.
Here's a link to the Opera 2.8 documentation, regarding the implementation of the File API, so it should work:
W3C File API support in Opera Presto 2.8
I've got a project using WebSockets that I want to possibly integrate with Kik. Is it going to be work on the Android platforms that don't natively support WebSockets? I know there are many posts here on SO with native android code to inject WebSockets into the webview. Have any of these been implemented? What is the suggested workaround if not?
Thanks!
WebSockets are natively supported on Android 4.4+. On older operating systems it is normally recommended to use XHR polling or other mechanisms.
I would suggest using Socket.io as it is a very mature library for this kind of technology with backward compatibility modes going back to pretty old browsers.
http://socket.io
To send debug messages from our web application to the browser, we have Firebug+FirePHP for Firefox, as well as Chrome Logger for Chrome/Chromium. FirePHP for Chrome does not work with the latest Chromium/Chrome versions and does not seem to get developed anymore.
Unfortunately, both tools are incompatible because they use a different format and thus require different server-side libraries.
Is there a way to make them compatible, or an alternative that works across browsers?
Webug for Chrome implements the FirePHP protocol, so FirePHP can be used cross-browser now.
I need a WYSIWYM markdown editor for my web application and I heard WMD was the obvious choice.
To my surprise WMD breaks in IE8. What other option do I have, or is there a version that's been tested on IE8 and is compatible?
Check out wmd-new. According to its website:
This version of WMD has been tested with IE 6, 7 and 8 RC1, Firefox 3, Safari 3.2, Chrome 1.0 and Opera 9.6. iPhone and iPod Touch support is rumored to work with the exception of the link/image prompt location. There are a few (minor) known issues with keyboard handling in IE and Opera. See the issues page for more details.
[...]
NOTE
Version 2.0 of this code was developed as a private bugfix/feature branch for Stackoverflow.com and is missing most of the optional features found in the original WMD as SO did not use them. Now that I'm putting this out on Google Code I'll be adding the new features back in v2.1 due out sometime in February 2009. Version 3.0 should be released in February/March 2009 and will a major rewrite making use of jQuery.
EDIT: I didn't notice it immediately but this project hasn't release any source code.
EDIT2: As pointed out by warren in a comment, a "Stack Overflow branch of WMD" is hosted on github. See Reverse Engineering the WMD Editor for more details.
I haven't used WYMeditor myself, but their supported browsers are:
Gecko-based browsers (Firefox 2.0+, SeaMonkey, Galeon, Epiphany, ...)
Microsoft Internet Explorer 6, 7 and 8
Opera 9.5+
Safari 3.1+
Google Chrome
The version of WMD on derobins' github should work fine with IE8.
There is one listed on the wikipedia page - but I've not used it: WYMeditor
I sugest Tinymce a wonderful Javascript WYSIWYG Editor, with loads of functionalities, and its opensource, it as versions for PHP, ASP, JSP and CouldFusion, multi language, and some others functions, very simple to customize with only the specific functions you want him to enable for your users.
Check out Tinymce website:
http://tinymce.moxiecode.com
Regards
EDIT:
I been using it for the past two years never had any problems with it.