10.5Fx Feature Parity

[GoogleCodeExporter]

"There are already some significant ways in which Firefox on Mac OS X 10.5 has 
fallen behind Firefox on newer versions of Mac OS X. Accelerated compositing, 
WebGL, and out-of-process plugins are not available on Mac OS X 10.5." -Josh Aas

Are all three theoretically possible?

Original issue reported on code.google.com by spm...@gmail.com on 17 Jul 2012 at 4:24

[GoogleCodeExporter]

Accelerated compositing and WebGL rely on getting the backend hardware working. 
I posted some ideas about that in 
http://tenfourfox.blogspot.com/2012/05/130-available.html

OOPP could work, but no PPC plugin is known to handle it.

But why are you posting this as an issue here and not for AuroraFox? Tiger 
can't ever support the first two, because OpenGL 1.2 doesn't do NPOT textures, 
and I won't do further plugin work other than what exists because of the 
security issue, so these aren't things *this* particular project is likely to 
fix.

Original comment by classi...@floodgap.com on 17 Jul 2012 at 1:22

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

For some reason your comment didn't stick, but I did get it in E-mail, so

My logic was what if we could meet his criticisms head on but of course
this does nothing against the prevailing IT ethos of the day (add an OS,
drop an OS, especially in the "minority" Mac market). What does it say of
an "Open Web" where our entire community is dropped for the holidays not to
mention the 10% mac userbase that actually has Intel and will be dropped as
well. I really wish they could drop XP/Leopard in tandem. I don't get the
culling users in time of crisis mindset. And of course this "upgrade push
from above" will force PPC users to migrate to Linux for version parity. If
they could give us until Q1 we could maybe put together an Australis 10.5
build that could in a way be publicity for Mozilla (not to mention giving
Apple a  gentle slap). Either way we're all in it together. Rambling
complete.

I'm certainly not disputing any of this, but this is a worklist and those 
specific features aren't something 10.4Fx specifically will be working on. 
That's the point I'm trying to make. This kind of stuff really belongs in a 
public blog, not rotting on a to-do list.

As far as 10.5 support goes, frankly the usual suspects wanted to axe it way 
back in 13, as you may recall. At least they were willing to compromise with me 
on the code issue even though on paper 17 will be "10.6 only" and I consider 
that a hard-won victory; they didn't have to be nice.

Original comment by classi...@floodgap.com on 17 Jul 2012 at 7:09

[GoogleCodeExporter]

Yes I'm afraid I was a tad unscrupulous in the above comment and I am
above all grateful to Mozilla, Apple, yourself, Tobias, Ben and
everyone who has made this possible. It is sad to see Firefox go but
we still have LW and I'm sure you will hack together an elegant
solution for Fx. I for one will not be going the Linux route at least
not yet (H.264 is now ironically Leopard's trump card).

Original comment by spm...@gmail.com on 17 Jul 2012 at 8:06

[GoogleCodeExporter]

And Tiger's with MacTubes I should add.

Original comment by spm...@gmail.com on 17 Jul 2012 at 8:08

[GoogleCodeExporter]

No worries. I will go ahead and mark this as Done unless there was anything 
else related to this specifically.

Original comment by classi...@floodgap.com on 17 Jul 2012 at 8:25

• Changed state: Done