Archived:HandleBrowserLoadEventL provides inaccurate size information (Known Issue)
Archived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.
Article Metadata
Tested with
Devices(s): Nokia N95, Nokia E90 Communicator
Compatibility
Platform(s): S60 3rd Edition, S60 3rd Edition FP1
Article
Keywords: MBrCtlLoadEventObserver
Created: User:Technical writer 1
(11 Jun 2008)
Last edited: hamishwillee
(21 Jun 2012)
Description
In order to observe load progress events of the browser control, the host application must implement the MBrCtlLoadEventObserver interface and its HandleBrowserLoadEventL() function.
The second parameter of HandleBrowserLoadEventL is TUint aSize which contains size information of the event. This size information is inaccurate. For example, using this information to estimate the total amount of data received will end up giving inaccurate results.
Regardless of the second parameter's inaccuracy, HandleBrowserLoadEventL() can still be used to observe events from the browser control.
Solution
No known solution.
Caoxiong - TBrCtlDefs:: EEventMoreUrlContentArrived Return current size
Size : 0 EEventMoreUrlContentArrived
Size : 1192 EEventMoreUrlContentArrived
Size : 2191 EEventMoreUrlContentArrived
Size : 3539 EEventMoreUrlContentArrived
Size : 6836 EEventMoreUrlContentArrived
Size : 9532 EEventMoreUrlContentArrived
Size : 13159 EEventMoreUrlContentArrived
Size : 13902 EEventMoreUrlContentArrived
Size : 15250 EEventMoreUrlContentArrived
Size : 16598 EEventMoreUrlContentArrived
Size : 16858 EEventMoreUrlContentArrived
Size : 17565 EEventMoreUrlContentArrived
Size : 17565 EEventMoreUrlContentArrivedcaoxiong 09:57, 7 September 2011 (EEST)