5 ms·

And here's the relevant snippet from Client/Frontend/Browser/Browser.swift: func createWebview() { if webView == nil { assert(configura

by rwl4 11y ago

And here's the relevant snippet from Client/Frontend/Browser/Browser.swift: func createWebview() { if webView == nil { assert(configuration != nil, "Create webview can only be called once") configuration!.userContentController = WKUserContentController() configuration!.preferences = WKPreferences() configuration!.preferences.javaScriptCanOpenWindowsAutomatically = false let webView = WKWebView(frame: CGRectZero, configuration: configuration!) ...

aaronbrethorst 11y ago
I forget where I read it, but someone from Mozilla stated somewhat recently(?) that, ultimately, Firefox is about a set of services shared across platforms, an experience, and a pledge to user privacy. It's not about a specific rendering engine.
- rockdoe 11y ago
  So much for open web standards? (Which definitely requires multiple implementations, that is to say competing rendering engines)
  - reubenmorais 11y ago
    That message is more for the Mozilla community than for the outside world. If Firefox for iOS implements WebRTC on top of Webkit, for example, that's a clear win for users. So Mozilla (the company) decided it's worth their money to make a Webkit browser and try to improve the situation on iOS little by little. But Mozilla (the community) is full of people with very strong ideas of the direction they want the organization to take, so the immediate reaction is for them to reject the idea – even core contributors. "Firefox without Gecko is not Firefox!". Instead of arguing whether branding a Webkit shell as Firefox is too big of a compromise, Mozilla (the leaders) redefines what the brand is about. This might seem silly, but it has a big impact on the community, by making it clear what the goals of the project are, and hopefully eliminating all the bikeshedding on what is and isn't Firefox. EDIT: I guess I never answered your question: open Web standards are still a priority for Mozilla, it's just that we've decided the little benefit for the user we can create by writing Firefox for iOS is also a priority.
    - arm 11y ago
      “If Firefox for iOS implements WebRTC on top of Webkit, for example, that's a clear win for users.” In its current state, at least, I wouldn’t call it a ‘clear’ win for users: https://news.ycombinator.com/item?id=9893561 https://news.ycombinator.com/item?id=9893561 https://news.ycombinator.com/item?id=9960504 https://news.ycombinator.com/item?id=9960504 https://news.ycombinator.com/item?id=9112717 https://news.ycombinator.com/item?id=9112717
- s_kilk 11y ago
  It's looking more and more like the future will be various browsers acting as branding and UI Chrome around Webkit/Blink.

by rwl4 11y ago

aaronbrethorst 11y ago

I forget where I read it, but someone from Mozilla stated somewhat recently(?) that, ultimately, Firefox is about a set of services shared across platforms, an experience, and a pledge to user privacy. It's not about a specific rendering engine.

rockdoe 11y ago
So much for open web standards? (Which definitely requires multiple implementations, that is to say competing rendering engines)
- reubenmorais 11y ago
  That message is more for the Mozilla community than for the outside world. If Firefox for iOS implements WebRTC on top of Webkit, for example, that's a clear win for users. So Mozilla (the company) decided it's worth their money to make a Webkit browser and try to improve the situation on iOS little by little. But Mozilla (the community) is full of people with very strong ideas of the direction they want the organization to take, so the immediate reaction is for them to reject the idea – even core contributors. "Firefox without Gecko is not Firefox!". Instead of arguing whether branding a Webkit shell as Firefox is too big of a compromise, Mozilla (the leaders) redefines what the brand is about. This might seem silly, but it has a big impact on the community, by making it clear what the goals of the project are, and hopefully eliminating all the bikeshedding on what is and isn't Firefox. EDIT: I guess I never answered your question: open Web standards are still a priority for Mozilla, it's just that we've decided the little benefit for the user we can create by writing Firefox for iOS is also a priority.
  - arm 11y ago
    “If Firefox for iOS implements WebRTC on top of Webkit, for example, that's a clear win for users.” In its current state, at least, I wouldn’t call it a ‘clear’ win for users: https://news.ycombinator.com/item?id=9893561 https://news.ycombinator.com/item?id=9893561 https://news.ycombinator.com/item?id=9960504 https://news.ycombinator.com/item?id=9960504 https://news.ycombinator.com/item?id=9112717 https://news.ycombinator.com/item?id=9112717
s_kilk 11y ago
It's looking more and more like the future will be various browsers acting as branding and UI Chrome around Webkit/Blink.