> One other consideration : The database is shared between Xwalk apps just like > Chromium but with the user of the app unable to clear the history (like > Chromium) it is potentially a problem. Do we want sharing between the > instances of Xwalk for such data? It needs to be carefully considered.
Li Yin: No, on Android platform, the inputing texts are stored on "DIR_ANDROID_APP_DATA", it is "/data/data/package_name/", which is only controlled by itself, not shared. And we also provide another API to clearFormData, which will clear all the stored autofilled data in the database. [Yongsheng] Li is right about this. Android provides system level app data protection for each app. Since auto complete data is app-specific even in crosswalk shared mode, I think it's not a problem. > Why we need these Java APIs? Why they need to be exposed? Who is going to use > them (you say "developer" but our developer are not Java people)? Is that > needed for the Cordova-container (I would assume no)? Li Yin: On Android platform, we are using XWalkSetting.java class to control the flags, which is same with Android WebView, it works fine on embedded mode. And I agreed with you, for Runtime, it is a must to add a JavaScript interface to control all the flags. I think we can implement them together in the future. [Yongsheng] Please note that those are not Java APIs but internal Java classes, which leverage the functionalities provided by Android SDK. Here Crosswalk only provides simple a class to be customized. Yongsheng
_______________________________________________ Crosswalk-dev mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
