Mozilla's Firefox Sync client submitted to Apple App Store

Re:Mozilla's Firefox Sync client submitted to Apple App Store by borisk on Wednesday June 30, 2010 @09:48PM (#1476781)

"with Apple’s prior written consent, an Application may use embedded interpreted code" - from the dev agreement. A few games have been approved to host an interpreter. So it's just a matter of Apple deciding if they want fully featured Firefox, Chrome, Opera or not.

[ Parent | on HN ]

Re:Mozilla's Firefox Sync client submitted to Apple App Store by mbrubeck on Wednesday June 30, 2010 @10:11PM (#1476817)

You left out part of it:

"Notwithstanding the foregoing, an Application may use embedded interpreted code in a limited way if such use is solely for providing minor features or functionality that are consistent with the intended and advertised purpose of the Application."

You might argue that executing JavaScript is a "minor feature" of a web browser. Then maybe Chrome would be allowed. But almost of Firefox's frontend is also written in JavaScript and tied to Mozilla's JavaScript engine. So there's no way that we (mobile Firefox) fall within the "in a limited way..." allowance.

[ Parent | on HN ]

Re:Mozilla's Firefox Sync client submitted to Apple App Store by cmelbye on Wednesday June 30, 2010 @10:43PM (#1476874)

They've approved interpreters for games for code that was written by the developers. I can't see them allowing an app that has a custom interpreter that users can use to run arbitrary code.

[ Parent | on HN ]

Re:Mozilla's Firefox Sync client submitted to Apple App Store by thought_alarm on Wednesday June 30, 2010 @10:15PM (#1476830)

A 3rd-party rendering engine is a security liability that Apple cannot control, therefore they won't allow it.

[ Parent | on HN ]

Re:Mozilla's Firefox Sync client submitted to Apple App Store by jistein on Wednesday June 30, 2010 @11:27PM (#1476953)

Apple would never allow it.

[ Parent | on HN ]