News for hackers. Stuff that matters.
Re:Firefox for iOS on GitHub by eclipxe on Thursday December 04, 2014 @11:24PM (#8703011)
Rendering engines are okay. Its the Javascript execution engine that is not allowed.

You can render all the HTML you want, you just can't allow untrusted code to be executed.

Re:Firefox for iOS on GitHub by air on Friday December 05, 2014 @12:55AM (#8703159)
> Rendering engines are okay. Its the Javascript execution engine that is not allowed.

No, they must use WebKit:

"Apps that browse the web must use the iOS WebKit framework and WebKit Javascript"

https://developer.apple.com/app-store/review/guidelines/

Re:Firefox for iOS on GitHub by eclipxe on Monday December 08, 2014 @02:49AM (#8715417)
You can render HTML content with a custom rendering engine - for example ePub ebooks are essentially bundled HTML + CSS content - there are several HTML rendering engines that read ePub ebooks but don't use Webkit.

Also, you can build a UI using web languages and render to native controls, all without using WebKit if you'd like.

Re:Firefox for iOS on GitHub by bzbarsky on Monday December 08, 2014 @02:59AM (#8715439)
Right, rendering HTML is fine. As long as you don't download it from the internet on-demand, or so.
Re:Firefox for iOS on GitHub by shadowmint on Thursday December 04, 2014 @11:54PM (#8703061)
Well, since you can't use the native javascript engine with a separate rendering engine, there's not much difference though is there?

(if you could, everyone would just do that to get dynamic behavior using javascript in their apps as a scripting language)

Re:Firefox for iOS on GitHub by eclipxe on Monday December 08, 2014 @02:50AM (#8715422)
Not all content created with web technologies and renderable with an HTML/CSS rendering engine require Javascript