Re:Google's playing the closed-open game again, this time wi...
by pornel on Wednesday July 27, 2011 @02:23PM
(#2813390)
That would explain blocking of Firefox, but they're blocking Safari and WebKit nightly and... everything else that doesn't have "Chrome" in User-Agent string: http://yfrog.com/z/kh1rylsqj
Re:Google's playing the closed-open game again, this time wi...
by mrpollo on Wednesday July 27, 2011 @03:45PM
(#2813779)
i just tried accessing the app with Safari and it came to my attention that its trying to load mp4 and mp3 files instead of the webm videos
http://yfrog.com/h7x8xup
then i got even more curious and found this file
http://www.allisnotlo.st/static/js/VideoList.js
look around line 236
this.src = src.replace(/(\.webm+)$/, (navigator.userAgent.indexOf('Chrome/') == -1 && (navigator.userAgent.indexOf('MSIE') != -1 || navigator.userAgent.indexOf('Safari/') != -1)) ? '.mp4' : '.webm');
but looks like they didn't upload any mp4 files :( sad
Re:Google's playing the closed-open game again, this time wi...
by pornel on Wednesday July 27, 2011 @04:08PM
(#2813882)
None of this '90s-style sniffing is necessary: HTML5 supports multiple <source> elements allowing browser to choose and has canPlayType('video/webm') for JavaScript.
Re:Google's playing the closed-open game again, this time wi...
by khuey on Wednesday July 27, 2011 @11:55PM
(#2815318)
Huh? Where do you see a sync XHR in there?
Re:Google's playing the closed-open game again, this time wi...
by mrpollo on Thursday July 28, 2011 @07:24PM
(#2819430)
there is none, my mistake
Re:Google's playing the closed-open game again, this time wi...
by ootachi on Thursday July 28, 2011 @12:23AM
(#2815366)
Er... there is no synchronous XHR in the snippet you pasted. All calls to open() pass true for the third parameter.
Re:Google's playing the closed-open game again, this time wi...
by mrpollo on Thursday July 28, 2011 @07:24PM
(#2819428)
You are right, the error i get on my console isn't related to that, i misunderstood the error i get, i tried replicating today and the xhr request goes trough ok, http://yfrog.com/gysa24p makes me wonder what was my original problem, ill try to stop commenting by impulse.
Re:Google's playing the closed-open game again, this time wi...
by angryasian on Wednesday July 27, 2011 @01:59PM
(#2813264)
this article is written with the obvious intention of bashing google, the writer didn't even do his research because honeycomb 3.2 source is available.
Re:Google's playing the closed-open game again, this time wi...
by tsuraan on Wednesday July 27, 2011 @02:26PM
(#2813401)
Where? http://source.android.com/ just says 2.3 is available, and google isn't turning up anything either.
EDIT: looks like the GPL/LGPL parts have been released (according to news reports, anyhow). Can you point me to a full buildable android 3.2 repo?
Re:Google's playing the closed-open game again, this time wi...
by darshan on Wednesday July 27, 2011 @02:45PM
(#2813505)
Only the GPL/LGPL parts are available, but the Honeycomb code isn't viewed as ready for public consumption yet. My guess is that we'll finally see the code when Ice Cream Sandwich rolls out.
Re:Google's playing the closed-open game again, this time wi...
by jackolas on Wednesday July 27, 2011 @03:51PM
(#2813806)
Some openness. Waiting for corporations to deem it fit for public scrutiny but not public usage? Makes me suspicious if they released all the GPL'd parts or if they missed some.
Re:Google's playing the closed-open game again, this time wi...
by starwed on Wednesday July 27, 2011 @04:23PM
(#2813944)
Sure, but that was exactly what the author meant.
Re:Google's playing the closed-open game again, this time wi...
by Toady on Wednesday July 27, 2011 @05:07PM
(#2814131)
Oh, okay, so that makes it okay for the site to be Chrome-only despite Google's constant proselytizing over "openness."
Re:Google's playing the closed-open game again, this time wi...
by mrpollo on Wednesday July 27, 2011 @03:58PM
(#2813840)
"this article is written with the obvious intention of bashing google" i agree, it is way faster to develop for just 1 browser, plus we should be celebrating people are trying to break ground doing this awesome videos, i can only begin to imagine all the impressive work that what went into this video, good one google +1
i was doing some research on it and they appear to be using sync xhr calls which causes FF to hiccup even after all this time.
https://bugzilla.mozilla.org/show_bug.cgi?id=383304 https://bugzilla.mozilla.org/show_bug.cgi?id=313646
they are marked as resolved but i just confirmed the xhr sync calls dont work in some cases.
google is using the sync calls here http://www.allisnotlo.st/static/js/API.js
Here you can try this to try and play the video on FF https://gist.github.com/1109890
you will notice your console throws some errors around line 42 of that file, if anyone knows what else is wrong here please let me know.