Bug 11152

Summary: Loading locks up the browser on mobile devices
Product: WebKit Reporter: David Carson <dacarson>
Component: Page LoadingAssignee: David Carson <dacarson>
Status: RESOLVED FIXED    
Severity: Normal CC: zalan
Priority: P2    
Version: 420+   
Hardware: Other   
OS: All   
Attachments:
Description Flags
patch
none
Corrected patch after Zalan's comment darin: review+

David Carson
Reported 2006-10-04 08:01:03 PDT
When loading large sites on mobile devices, the browser often feels like it locks up. The user can not navigate the partially loaded content.
Attachments
patch (2.18 KB, patch)
2006-10-04 08:11 PDT, David Carson 		no flags
DetailsFormatted DiffDiff
Corrected patch after Zalan's comment (2.17 KB, patch)
2006-10-04 09:21 PDT, David Carson 		darin: review+
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
David Carson
Comment 1 2006-10-04 08:11:17 PDT
Created attachment 10900 [details] patch The tokenizer chunk size is quite large for low CPU devices, which results in the browser spending all it's time in the tokenizer. With a smaller chunk size, the tokenizer yields more often allowing the browser to respond to key events, etc. With the smaller chunk size, the tokenizer should not need to wait as before resuming tokenizing.
alan
Comment 2 2006-10-04 09:16:40 PDT
'#define MOBILE 0' makes '#ifdef MOBILE' true, use #if MOBILE instead.
David Carson
Comment 3 2006-10-04 09:21:00 PDT
Created attachment 10901 [details] Corrected patch after Zalan's comment Changed #ifdef MOBILE to #if MOBILE
Darin Adler
Comment 4 2006-10-05 07:49:56 PDT
Comment on attachment 10901 [details] Corrected patch after Zalan's comment The only thing I'm concerned about here is that there's a comment that mentions 200ms in the non-mobile case, but for some reason the we are using 300ms for the mobile case. r=me
Mark Rowe (bdash)
Comment 5 2006-10-05 14:43:55 PDT
Landed in r16821.
Note You need to log in before you can comment on or make changes to this bug.