mozjs52, 60, and 68 all build on 10.6.8 now via MacPorts, and up to 60 are available for ppc Tiger I believe.
Those js versions all fully support the async/await features that so many websites like github and others are using now, that are a thorn for TenFourFox.
I tried just changing the "js" binary in the bundle to a symlink to a MacPorts-installed mozjs 52, 60, and 68, but that does not seem to be enough to actually make the websites work.
Do you have an idea how someone might go about using one of those external mozjs versions?
Does TFF call into a js-supporting library (ie does the js version have to be the same architecture?) or does it just call the binary as a js-interpreter, andcould you for example use an x86_64 mozjs binary from an i386 TenFourFox.
Many, most, or all the subparts of TenFourFox are available as ports in MacPorts -- perhaps factoring it out like that would keep it more maintainable?
mozjs52, 60, and 68 all build on 10.6.8 now via MacPorts, and up to 60 are available for ppc Tiger I believe.
Those js versions all fully support the async/await features that so many websites like github and others are using now, that are a thorn for TenFourFox.
I tried just changing the "js" binary in the bundle to a symlink to a MacPorts-installed mozjs 52, 60, and 68, but that does not seem to be enough to actually make the websites work.
Do you have an idea how someone might go about using one of those external mozjs versions?
Does TFF call into a js-supporting library (ie does the js version have to be the same architecture?) or does it just call the binary as a js-interpreter, andcould you for example use an x86_64 mozjs binary from an i386 TenFourFox.
Many, most, or all the subparts of TenFourFox are available as ports in MacPorts -- perhaps factoring it out like that would keep it more maintainable?