3 ms·

Firefox on iOS https://appsto.re/ca/-LZ_6.i https://appsto.re/ca/-LZ_6.i

captainmuon 11y ago
That one uses WebKit. I wonder if anybody actually got Gecko to run on iOS. As I understand, there are "only" two problems - Apple not allowing other HTML/JS implementations, and Apple not allowing writable, executable memory. I don't know what the status of the first is, but you can get around the latter by just using an interpreter instead of a JIT (which is of course terribly slow). Or, you decide Apple is never going to let your engine on the App store, and then you just include the JIT. The enforcement is done at time of submission to the app store, not at runtime. IIRC, you can just call a certain function to mark a memory region as writable or executable, but Apple detects this call statically. I further wonder if you could just distribute binaries, outside of the app store, and your users would have $99 developer accounts, and run a little script to "build their project with XCode", signing and installing it to their device?
- cpeterso 11y ago
  Prototype builds of Gecko running on iOS do exist, but they are not officially developed or maintained by Mozilla. You can track the progress of merging iOS support into the main Firefox repository in this bug: https://bugzil.la/1163827 https://bugzil.la/1163827
  - st3fan 11y ago
    That looks pretty official to me.
    - cpeterso 11y ago
      Well, you certainly know more about Mozilla's iOS plans than I do :) but I thought Ted was just working on the patches on his own time, not in any official capacity.
- amake 11y ago
  You no longer need a paid developer account to deploy apps from source to a physical device.
- st3fan 11y ago
  Isn't the enforcement done at runtime? I remember testing this and the mprotect() call was simply giving me a EPERM back or so.
empyrical 11y ago
It uses WebKit rather than Gecko due to the appstore restrictions though
- 0942v8653 11y ago
  And it's not available on the AppStore for U.S. people yet (I had to build it myself).
  - st3fan 11y ago
    We will do a global release soon.

That one uses WebKit. I wonder if anybody actually got Gecko to run on iOS. As I understand, there are "only" two problems - Apple not allowing other HTML/JS implementations, and Apple not allowing writable, executable memory. I don't know what the status of the first is, but you can get around the latter by just using an interpreter instead of a JIT (which is of course terribly slow). Or, you decide Apple is never going to let your engine on the App store, and then you just include the JIT. The enforcement is done at time of submission to the app store, not at runtime. IIRC, you can just call a certain function to mark a memory region as writable or executable, but Apple detects this call statically. I further wonder if you could just distribute binaries, outside of the app store, and your users would have $99 developer accounts, and run a little script to "build their project with XCode", signing and installing it to their device?

cpeterso 11y ago
Prototype builds of Gecko running on iOS do exist, but they are not officially developed or maintained by Mozilla. You can track the progress of merging iOS support into the main Firefox repository in this bug: https://bugzil.la/1163827 https://bugzil.la/1163827
- st3fan 11y ago
  That looks pretty official to me.
  - cpeterso 11y ago
    Well, you certainly know more about Mozilla's iOS plans than I do :) but I thought Ted was just working on the patches on his own time, not in any official capacity.
amake 11y ago
You no longer need a paid developer account to deploy apps from source to a physical device.
st3fan 11y ago
Isn't the enforcement done at runtime? I remember testing this and the mprotect() call was simply giving me a EPERM back or so.

empyrical 11y ago

It uses WebKit rather than Gecko due to the appstore restrictions though

0942v8653 11y ago
And it's not available on the AppStore for U.S. people yet (I had to build it myself).
- st3fan 11y ago
  We will do a global release soon.