Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

zorinlynx

macrumors G3
Original poster
May 31, 2007
8,453
19,314
Florida, USA
There were reports that in 4.3, web views within applications (like when you tap on a link in the Twitter app) were using the older (slower) rendering engine and not the new one from 4.3 Safari.

Did they fix this in 4.3.1? Just wondering if it's worth upgrading my iPad (and possibly ruining my chance to have a jailbreak sooner)
 
There were reports that in 4.3, web views within applications (like when you tap on a link in the Twitter app) were using the older (slower) rendering engine and not the new one from 4.3 Safari.

Did they fix this in 4.3.1? Just wondering if it's worth upgrading my iPad (and possibly ruining my chance to have a jailbreak sooner)

NOPE, still getting checkerboard.
 
It's going to take a while for the Nitro JavaScript engine to work in anything apart from Safari because it's a potential security problem. Nitro works by converting JavaScript into native code and then running the native code. Normally on iOS applications are not allowed to do this and instead can only run code loaded from disk. This restriction makes it harder to write viruses and other nasties. It also means that Apple can be more confident that the code that gets submitted to the App Store is the code that runs on people's devices. To allow Nitro to work Safari has been given a exception to this restriction.

For more details have a look at Gruber's article. That article also suggests that the problem will be solved when the Webkit2 engine is introduced. Webkit2 introduces a multi-process model that should allow application web views to take advantage of Nitro.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.