hsivonen

55 ms·

511.
by hsivonen 13y ago
From a person involved with this at Cisco: "All the build scripts etc that Cisco uses will be part of the open source project so that anyone can build it them selves and check that their build matches the Cisco binary and check the cod
512.
by hsivonen 13y ago
There is no need to reverse engineer H.264. The spec is not secret. VLC operates out of France--not the U.S.
513.
by hsivonen 13y ago
Why do you say Mozilla could not view or audit the source? Cisco announced source release, too.
514.
by hsivonen 13y ago
You should try sending OpenBSD-targetin cross-compilation scripts to Cisco.
515.
by hsivonen 13y ago
> How is this a victory over using GStreamer and using the encoders/decoders available on the OS? MPEG-LA-licensed GStreamer codecs cost 28 euros to the end user. This priced at zero towards the end users. This is not a particular w
516.
by hsivonen 13y ago
The rationale for preferring 128-bit AES over 256-bit AES is given later in the doc.
517.
by hsivonen 13y ago
On the topic of the HTML parser, you may be interested in https://developer.mozilla.org/en-US/docs/Mozilla/Gecko/HTML_...
518.
by hsivonen 13y ago
The reason why the parser was written in Java in the first place was that it was written for the Validator.nu HTML validator. The validator was written in Java, because Java had the best set of Unicode-correct libraries for the purpose and
519.
by hsivonen 13y ago
A browsing context doesn't start its life empty. Instead, when a browsing context is created, if a JS program looks at what's in there, there's an about:blank doc in there. Since you can create a browsing context synchronousl
520.
by hsivonen 13y ago
Rhino code is not involved. The portable core of the HTML parser is maintained as Java. However, the translation is not done during the Firefox build process. Instead, the translation is triggered manually when the Java code changes and the
521.
by hsivonen 14y ago
No, EME is an API that the browser exposes to site-supplied JavaScript code. The JavaScript code uses EME to talk with a Content Decryption Module (CDM) whose exact characteristics (including the protocol you talk with it; EME sees byte buf
522.
by hsivonen 15y ago
I was wrong to claim Chrome didn't send Accept-Charset. Before I wrote the post, I opened another charset-related test case in Chrome (on two operating systems even) and after opening that URL and the relevant URL in various browsers though
523.
by hsivonen 15y ago
Yes, it counts Chrome as supporting H.264. Only IE9 and above support <video>, so the share of IE8 and older doesn't count as H.264 share. Firefox 9 has a larger usage share than IE9. (I included the script so that people could read
524.
by hsivonen 15y ago
Yes. The whole point of the post is to consider <video> support.
525.
by hsivonen 15y ago
The Firefox PPA that corresponds to the Chrome dev channel is https://launchpad.net/~ubuntu-mozilla-daily/+archive/firefox...
526.
by hsivonen 15y ago
Firefox has improved a lot since Firefox 3.6. Firefox 3.6 was released on 2010-01-21. Firefox 8.0 was released on 2011-11-08. (Chrome 14 was released on 2011-09-16.) I suggest comparing the latest Firefox (8) with the latest Chrome (15). (D
527.
by hsivonen 16y ago
Other things were mentioned already, so not to repeat those: On Ubuntu in particular (but on other Linux distros, too), Firefox 4 has a more platform-appropriate appearance and feel than the other cross-platform major browsers (Chrome and O