Anxiety is building in the Power Mac community now that Mozilla has officially announced 3.6 is dead, and no one is really sure what will happen to Camino (they still make updates, and historically they have maintained old branches after Firefox versions based upon it have ceased, such as 3.0 (Camino 2.0/Mozilla 1.9.0), but there is no clear future for the project and Mozilla 1.9.2 is quite long in the tooth by now). Some people are bailing out for Linux, and there are some nice options there. I tried Lubuntu 12.04 on my 867MHz TiBook which normally runs OS 9, and the LiveCD was very impressive. I missed having the JIT in Firefox, though ...
Nevertheless many of us, including yours truly, will remain 10.4 (and 10.5) users simply because we need the software options and/or Classic, and the browser options will continue to dwindle. Since Mozilla has indicated us as their official recommendation to Power Mac users going forward, we want to make sure we are covering all bases, which is why SUMO entries like this and this Mozillazine thread (possibly the same user) really cheese me off. Thanks, sport, for slamming the project in public (in so many words, "I think it's nice but it sucks") and then admitting in that same SUMO thread that you haven't even bothered to report your issue(s) to us, whatever they actually are. I can't fix what I don't see, but I don't even look unless you tell me about it. Chris and Theo are on the job in the support area, plus whatever crack users are around, plus myself. There's no excuse for not reporting issues as pervasive as this user claims to be experiencing anymore; we have the infrastructure and we have the volunteers to at least triage it. If we can't fix it, well, I suppose I can't blame someone for having a bad opinion of the software in that case (justified or not), but not even giving us a chance is just plain mean.
Also, yes, we know Mozilla has thrown in the towel and is working on an H.264 solution, so please stop E-mailing me, posting support threads about it, etc. A couple of notes: 1) it's going to have to involve QuickTime; I am very leery of the legal risk I or others would assume if we embed ffmpeg because there is no exception for decoders, even not for profit and 2) while it will be faster than WebM, it will still be slower than the QTE because the QTE doesn't have to composite the video and can use OpenGL hardware to accelerate display, whereas we still have to composite, scale, etc., the video in TenFourFox. Please keep these issues in mind (and accept that I won't enable the option if it turns out Mozilla won't support QT or uses a QT X-only API). I am really hoping Mozilla's legal counsel issues some opinion on this that those of us downstream can take to the bank.
As soon as Mozilla finishes with 10.0.4, which is usually week 3 or 4 in the cycle, we will push out a go-to-build, and hopefully 12 will be out by then too.