Saturday, July 25, 2020

TenFourFox FPR25 available

TenFourFox Feature Parity Release 25 final is now available for testing (downloads, hashes, release notes). There are no additional changes other than outstanding security updates. Assuming all goes well, it will go live on Monday afternoon/evening Pacific time.

For FPR26 there will be one additional change to DOM workers and I'm looking at some problem sites to see if there are some easy fixes. Still, the big issues continue to be the big issues and we'll just have to do things like the AppleScript workarounds to deal with them better in future. I'd like to see more people experimenting with AppleScript, too -- we have a whole page of documentation devoted to it and some examples which you can download if you don't want to type them in.

Meantime, did you know Apple had LocalTalk cards for the PC?


  1. Apparently, there are concerns about the status of core-js project (referenced in the comments on the FPR24 post from June 27)
    State and governance of the project?

    but one of the comments on that core-js issue mentioned

    "For those in need of an immediate replacement, may provide what you need (and the project welcomes maintainers, if you feel like contributing)"

    Do any of the sub-projects look like they would help with current TFF issues?

    1. We actually implement almost all of those shims natively. What we're missing is async/await, and I do not know of any polyfill that supplies it. There are some preprocessors that convert them into third-party coroutines with some success, but they work on the server side and there's nothing client-side that can do it on the fly that I've seen. If you've seen something that might, I'll all ears.

  2. By the way shouldn't the CPU version part of the About window?

    1. That's not a bad idea. Should be easy enough to add.

  3. Hey CK: I'm noticing a wierd thing with eBay - it is returning the mobile version, eventhough the user agent is sent to default. Isn't happening however with a foxbox?



Due to an increased frequency of spam, comments are now subject to moderation.