3 ms·

I thought all browsers on iOS were using the apple browser engine and ditto for Android. That is, they are just skins

• JimDabell 2y ago
  They are using the WebKit rendering engine, but there’s a lot more to a web browser than just its rendering engine. They aren’t just skins.
  • ctxc 2y ago
    Could you add a more to that? What other complex parts are built by FF?
    • fmbb 2y ago
      What do you think is complex?
    • matsemann 2y ago
      Not necessarily complex, but the tab switcher etc is built by Firefox, and probably is what tries to load the favicons to display the icon somewhere?
    • JimDabell 2y ago
      Why the “complex” qualifier? The code responsible for the incorrect favicon URL bug is very simple, and part of the Firefox codebase not WebKit: https://github.com/mozilla-mobile/firefox-ios/blob/bd589c194fbb5f16bc3748a276762f92b0ce4185/BrowserKit/Sources/SiteImageView/FaviconURLProcessing/URLFetcher/FaviconURLFetcher.swift#L66 https://github.com/mozilla-mobile/firefox-ios/blob/bd589c194... Firefox on iOS has about 200k lines of Swift. As a rough rule of thumb, everything that isn’t directly related to rendering something within the page or executing JavaScript is Firefox code not WebKit code. So bookmarks, syncing, tabs, etc.
• mcfedr 2y ago
  Yea, that's basically it on iOS, although there is a bunch ux, so it's not nothing On android, browsers can ship their own engines, and they do. There is actually some freedom on android.
• dizhn 2y ago
  This changed very recently due to EU rules