×
Namespaces

Variants
Actions
Revision as of 09:55, 15 June 2012 by hamishwillee (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Archived:Browser Control interface stops working after delete/reconstruct (Known Issue)

From Nokia Developer Wiki
Jump to: navigation, search

Archived.pngArchived: 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}}.

An instance of the Browser Control interface class does not work properly after it has been deleted and reconstructed on S60 3rd Edition.

Article Metadata
Compatibility
Platform(s): S60 3rd Edition
S60 3rd Edition (initial release)
Article
Created: User:Technical writer 1 (20 Aug 2007)
Last edited: hamishwillee (15 Jun 2012)

Description

When an instance of the Browser Control interface (CBrCtlInterface) is constructed (see CBrCtlInterface::CreateBrowserControlL()), the interface will remain functional until the end of its life cycle. However, if the object is deleted and another one is created in the same session, the Browser Control API stops working. No errors are returned, but Web content will not be rendered onto the parent control anymore.

How to reproduce

This issue can be reproduced with the BrCtlSampleApp example application from the S60 3rd Edition SDK. The example application deletes and reconstructs the CBrCtlInterface object for each test case (whenever the capabilities for browser control are changed).

Solution

Add the following line after every CreateBrowserControlL() function call:

iBrCtlInterface->ActivateL()
This page was last modified on 15 June 2012, at 09:55.
181 page views in the last 30 days.