The AJAX apps at bindows.net do not open. Most operate under FireFox, although a few appear to identify the UserAgent and indicate that they only work with IE/Win.
Some examples: http://bindows.net/bindows/samples/applauncher/ http://bindows.net/bindows/samples/inline/ http://www.bindows.net/bindows/samples/apibrowser/
Stock Safari 2.0.2 just doesn't work with samples, while a nightly build is identified as unsupported, and links are hidden from the page (but the behavior when using direct links is actually the same).
Reassigning to webkit-unassigned for more exposure.
We have an internal branch of Bindows that is working in Safari but issue #7138 is currently a blocker for us.
So, I'd like to reduce this bug. Unfortunately, all your examples seem to derive their behaviour from the minimized JS in http://www.bindows.net/bindows/html/js/application.js or the files it loads. Any chance we could get an example that isn't obfuscated?
We released Bindows 4.0 a while back which fully supports webkit. http://www.bindows.net/documentation/40/ Bindows apps are running like a dream in Safari and Chrome etc. You can close this bug.
As of 07/17/2010, as far as I can tell from observation the referenced examples work in Mac Safari version 5.0 (6533.16) and behave like in Mac Firefox 3.6.3. These observations seem to agree with the Bindows 4.1 information page <http://www.bindows.net/documentation/Bindows41.html> (last updated 06/28/2010), which claims support for Safari 4 (*), the associated Bindows.net release notes <http://www.bindows.net/bindows/releasenotes.html>, and Johan Lund's comment <https://bugs.webkit.org/show_bug.cgi?id=4986#c6>.. Therefore, I am closing this bug. If there are any existing issues, feel free to re-open this bug and/or file a new bug(s). (*) "Bindows 4.1 supports the latest versions of all the major browsers, including IE8, Firefox 3.6, Safari 4, and Chrome."