tschneidereit

7 ms·

31.
by tschneidereit 12y ago
Media codecs are a very common source of security holes, which is one of the main reasons for not indiscriminately using just any codec that might be installed on the system. I think most users value the decision to not unnecessarily expose
32.
by tschneidereit 12y ago
I think letting the browser do this kind of caching for you is best in most cases. Developers have used tricks to force browsers to layerize content for many years, and browsers have become better at that over time. Nowadays, it should be f
33.
by tschneidereit 12y ago
This is indeed a major consideration: Flash will undoubtedly go away as a player, and if we don't want to lose all the legacy content with it as if it were stored on floppy disks, Shumway or something like it is the only solution. Note
34.
by tschneidereit 12y ago
(Shumway tech lead here) Somewhat absurdly, you currently need Flash to use Flash without Flash in many cases. We don't yet have support for installing Shumway in navigator.plugins, so sites that detect Flash using that (i.e., most of
35.
by tschneidereit 12y ago
Structs are coming to JS proper in the form of Typed Objects. For a whole load of details, check the spec draft ( https://github.com/dslomov-chromium/typed-objects-es7 ) or this very readable paper: http://sma
36.
by tschneidereit 12y ago
We're moving away from the attach-patches-to-bugs model, but in another direction: bugzilla integration with reviewboard, with changesets pushed to a review server and review requests being triggered automatically. See https:/&#x
37.
by tschneidereit 12y ago
Full support for contributing to Firefox via git is coming: http://glandium.org/blog/?p=3413
38.
by tschneidereit 12y ago
Several things: As of recently, that trend has finally stopped: Firefox has started gaining (very) small amounts of market share recently. The point where the speed of user attrition slowed down was actually slightly before the Australis la
39.
by tschneidereit 12y ago
That makes a lot of sense, yes. We can profile cases like that and get info/help from people working on the relevant components. It happens fairly frequently that we move perf bugs from the JS component into GFX or DOM bindings or some
40.
by tschneidereit 12y ago
(SpiderMonkey engineer here) What VerGreeneyes says is true for our JS engine, too: you can always file bugs in our bugzilla (in the "Core/ JavaScript Engine" component). We react to such bugs very promptly (as you can see in