[ 
https://issues.apache.org/jira/browse/CB-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13490988#comment-13490988
 ] 

Joe Bowser commented on CB-1811:
--------------------------------

Yes and no. There are a few primary builds of the browser based on what device 
tree they're based on.  All Samsung devices should have the same build, and 
since I tested it on Samsung, I would be tempted to say that I can't reproduce 
it.

Nexus devices are based on AOSP.
HTC and other Qualcomm based-devices are based on the CodeAurora Android tree.
Motorola and other OMAP based devices are based on the OMAP Android tree.
Samsung Exynos based devices are based on their own special Android tree.
Intel Atom based Android devices have their own tree.

In addition, certain other manufacturers will also have other special trees, 
such as the LG Optimus 3D, which has its own webkit that slows down input and 
output from the WebKit bridge.  This drives me up the wall, since I can't just 
tell people to root their devices and run CyanogenMod (yet another Android 
tree, based off AOSP).

                
> Previously hidden select dropdowns crashing the webview when focused upon
> -------------------------------------------------------------------------
>
>                 Key: CB-1811
>                 URL: https://issues.apache.org/jira/browse/CB-1811
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Android
>    Affects Versions: 2.1.0, 2.2.0
>         Environment: Samsung Galaxy S3 (Android 4.0.4)
>            Reporter: Adam 
>            Assignee: Joe Bowser
>            Priority: Minor
>              Labels: bug, crash
>
> I have a div panel that is hidden when a page is first shown. Inside the div 
> are a few html dropdowns (select tags). When I make the div visible (via 
> javascript) and focus into one of the dropdowns, I get the following logcat 
> error:
> 11-04 03:58:49.136: A/libc(18437): Fatal signal 11 (SIGSEGV) at 0x00000000 
> (code=1)
> Then, the app just crashes and the webview disappears. I confirmed that this 
> happens when the parent div is initially invisible (display:none). If the div 
> is visible at first, all works fine, even if the div is hidden subsequently.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to