Firefox for iOS on GitHub

fabrice_d wrote: post #3

0x006A wrote: post #2

is this a mirror or did the main development move to github?

That's the main repo. It was private before.

So Firefox repos are moving to github instead of hg.mozilla.org or git.mozilla.org?

Re: Firefox for iOS on GitHub

#5

Post by 0x006A » Fri, Dec 05, 2014, 12:40 AM UTC

- How far away from a release is this?

- Given that Apple does not allow other render engines. What makes this Firefox?

Re: Firefox for iOS on GitHub

#6

Post by fabrice_d » Fri, Dec 05, 2014, 12:59 AM UTC

0x006A wrote: post #4

fabrice_d wrote: post #3

Earlier quoted context omitted.

That's the main repo. It was private before.

So Firefox repos are moving to github instead of hg.mozilla.org or git.mozilla.org?

Not the main gecko repository, no.

Re: Firefox for iOS on GitHub

#7

Post by [deleted] » Fri, Dec 05, 2014, 1:09 AM UTC

0x006A wrote: post #5

- How far away from a release is this? - Given that Apple does not allow other render engines. What makes this Firefox?

[deleted]

Re: Firefox for iOS on GitHub

#8

Post by dubcanada » Fri, Dec 05, 2014, 1:11 AM UTC

0x006A wrote: post #5

- How far away from a release is this? - Given that Apple does not allow other render engines. What makes this Firefox?

Well according to tweets, not very far.

And with the release of WKWebView, I guess it makes it a skin.

Re: Firefox for iOS on GitHub

#9

Post by misiti3780 » Fri, Dec 05, 2014, 1:13 AM UTC

Looks like a great Swift reference! Nice work!

Re: Firefox for iOS on GitHub

#10

Post by micampe » Fri, Dec 05, 2014, 1:16 AM UTC

0x006A wrote: post #5

- How far away from a release is this? - Given that Apple does not allow other render engines. What makes this Firefox?

> What makes this Firefox?

I think that's an interesting question. Is a browser defined by its rendering engine or by its features and UI?

When Chrome used WebKit, it was clearly understood by everyone to be different from Safari, even though the rendering engine was the same (I know, the differences were big), but a Firefox browser that uses WebKit seems to not be considered Firefox.

Personally, while I understand the philosophical and political differences, I think the browser is defined by its features, not the rendering engine: the user wants their bookmarks to sync between the phone and the computer, they don't care whether the two programs use the same library to draw the page on the screen or not, just like they don't care which malloc() implementation they use.

To put it in fewer words: Chrome on iOS is still Chrome, not Safari, because it has Chrome's features.

(This would not have been true a decade ago, but rendering engines compatibility is much less of an issue now)