Hi, Stefan Actually, XWalkCoreShell is using ViewPager to contain two XWalkView instances. You can get it in test_apks package from https://download.01.org/crosswalk/releases/crosswalk/android. I’ve been trying to reproduce the issue you described on XWalkCoreShell (extends tab count to 4 locally), it doesn’t appear.
Basically, behavior will be quite different depends how you implement your pageAdapter, especially the part how you reuse the fragment. For xwalkView cases, suggestion is to never reuse Fragment. And to keep it from being destroyed and re-created all the time, I suggest to call mViewPager.setOffscreenPageLimit(4) in your case. Thanks, Shiliu. From: Crosswalk-help [mailto:[email protected]] On Behalf Of Stefan Persson Sent: Wednesday, August 27, 2014 3:46 AM To: [email protected] Subject: [Crosswalk-help] Embedding XWalkView in FragmentPagerAdapter Hi, In a project I am working in there is a requirement to have a ViewPager with FragmentPagerAdapter having 4 pages. Each page (fragment with one XWalkView instance / fragment) load different urls where the webpage is build using angular. Problem I have is that very often content from an other page then the one that is selected is showing up when I change pages. (When having selected page #2 the view from page #3 is visible) When I replace XViewView with build in ChromeClient in Android 4.4 it works perfectly. I have verified that the correct fragment and correct url is loaded for each page. I wonder if anyone have tried to do similar solution as me and if it is supported? If any one could give me some ideas on what to try out to get it to work? using crosswalk-webview-8.37.189.2-arm Tested on Nexus 5 and Samsung S3 with same result. Br Stefan
_______________________________________________ Crosswalk-help mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-help
