Skip to main content
Legend
March 26, 2013
Question

StageWebView loses interactivity after Event.DEACTIVATE > Event.ACTIVATE

  • March 26, 2013
  • 1 reply
  • 1031 views

Hi,

I have a StageWebView displaying an HTML page in Android with AIR (currently 3.5, but the same happens with 3.6). It displays fine and works perfectly, until...

If I flip out to another app, for example, by clicking on the device home button, and then return to the app, the StageWebView still renders my HTML correctly, and will load new pages correctly,

BUT...

Clicking links no longer has any effect. It appears there is some interaction as the mousedown link highlighting works as normal, but there is no navigation of the browser.

I will dig a bit deeper to see whether this happens with simple HTML links as well (I think the page uses jquery a lot) but this seems like a fairly fundamental bug. There doesn't appear to be any workaround - once the StageWebView stops working, the only remedy is to close the app and restart as even creating a new StageWebView instance doesn't appear to fix the issue.

Can you let me know whether this is a known issue with a known bug report or should I create a new one?

G

This topic has been closed for replies.

1 reply

chris.campbell
Community Manager
Community Manager
March 26, 2013

I'm not seeing anything jump out at me.  What version of Android are you using?  Is there anything special/different about the links?  I'd go ahead and open a new bug report on this over at bugbase.adobe.com.  When adding the bug, please include some sample code or an application so we can quickly test this out internally.  If you'd like to keep this private, feel free to email the attachment to me directly (ccampbel@adobe.com). 

Once added, please post back with the URL so that others affected can add their comments and votes.

Legend
March 27, 2013

Will do, it will be Friday before I am back on that project, though.

G

Legend
March 29, 2013

OK, I've added a bug report here: https://bugbase.adobe.com/index.cfm?event=bug&id=3532211

It looks as if there is a linkage with the way I'm handling deactivate / activate (browser is removed from stage on deactivate and added back on activate). I am investigating a workaround, but it may not be possible due to the project requirements...

However, surely, that still shouldn't affect anything?

G