The separation of "Firefox" (brand, UI, browser history, password sync, extensions, etc) from "Gecko" (an implementation of a rendering engine) seems like a good idea to me, even if it was forced by Apple.<p>Gecko stands for nothing; it's just code. Whereas the Mozilla / Firefox brand stands for things like privacy, security, etc. (<a href="https://www.mozilla.org/en-US/about/manifesto/" rel="nofollow">https://www.mozilla.org/en-US/about/manifesto/</a>)<p>The Firefox/Mozilla brand shouldn't be tied to Gecko or any other specific piece of code.
Here is a link to the repository, for those interested :<p><a href="https://github.com/mozilla/firefox-ios" rel="nofollow">https://github.com/mozilla/firefox-ios</a><p>It is programmed using Swift.
It's not clear to me why there's no link on the blog post (at least, I couldn't find one); but here's the product page, grabbed from one of the screen shots: <a href="https://www.mozilla.org/en-US/firefox/ios" rel="nofollow">https://www.mozilla.org/en-US/firefox/ios</a> .
I'm not very familiar with how web browsers are built, but would it be possible to write a HTML / CSS renderer on iOS that utilised JavaScriptCore for code execution?<p>This would abide by Apple's policies given that arbitrary code is still executed through their JavaScript engine, but would give much more flexibility on the rendering side.<p>It would be more bespoke than simply wrapping a WKWebView.<p>Is this a feasible path for a browser like Firefox on iOS?
What’s the setup for ‘default browser’ like on iOS now? I guess you can add Firefox as a target for ‘Send to’ sheets but presumably normal links in other apps will still open Safari?