<< Songs In My Head | The roads I take... | Integration eines Magento-2-Webshops mit FreeFinance und selbstgebautem Warenmanagement >>

Weekly Status Report, W34/2012

Here's a short summary of Mozilla-related work I've done in week 34/2012 (August 20 - 26, 2012):

The Firefox 15 releases we just shipped for desktop systems and Android (phones plus tablets!) are surely worth checking out - fewer add-on memory leaks, improved developer tools, Android tablet support and more are really nice highlights of this update.
What thrills me most though is that web technology is improving to make a lot of things possible in a website or web app that almost everyone thought to be impossible previously. And there are demo games to showcase those features, like BrowserQuest, which works nicely on desktop as well as mobile devices, and - hold your breath - a first-person shooter running smoothly in the browser! See Lawrence's blog post for more about that "BananaBread" demo, and a link to test it yourself (for the latter, you'll need Firefox 15 or newer, on Linux possibly even Firefox 16).

Seeing that in action, I have no doubts any more that the web can be a great platform even for gaming (and all that without OS boundaries mattering). ;-)

Entry written by KaiRo and posted on August 28th, 2012 19:42 | Tags: L10n, Mozilla, SeaMonkey, Status | 2 comments | TrackBack




are plugin-container deadlocks part of crashkill?
Hi o/
There's a bunch of deadlocks between plugin-container and firefox reported on bugzilla, some quite old. Most are easy to reproduce.
Some are confirmed, some are not, but all are unowned with no sight of progress.

My question is: are they, or should they be, part of CrashKill effort? Is there anything I can do (short of writing a patch myself) to push them forward somehow?

I'm suffering from them daily :(
2012-08-29 04:17



I'm not completely sure what you are referring to, but please point me to a few of those bugs.
If this is Flash hangs, we follow them quite a lot, and they're entirely Adobe's fault, but we're trying to help them find fixes (not that easy when you can't see their code, though).
2012-08-29 17:21

Add comment