Known limitations of Qt5's Webkit2 implementation:
- Web storage (including cookies, web storage and web sql, but excluding preferences) is stored between web applications, posing a security threat
- Web access cannot be controlled, i.e. all web applications may access any URIs without restrictions
- Synchronous JavaScript platform APIs are challenging/impossible due to not being able to invoke C++ code synchronously
- Web application folder based localization is not possible (always reverting to default language)
- Unable to change user agent string of the web interface, possibly resulting in denied access to Firefox Marketplace (working to overcome this somehow..)
Current overall progress with the Sailfish port:
- Core functionality port to Qt5: Done
- Sailfish manager UI: Ongoing (~70%)
- Sailfish web application UI: Ongoing (~50%)
- Sailfish cover view supporting minimized web application: Ongoing (~50%)
- Refactoring Widget API to work with Webkit2: 0%
- Refactoring platform APIs to work with Webkit2: 0%
- Reintegrate Cordova: 0%
- Rewriting Firefox OS config parsing: 0%
- Multiprocess support via D-Bus: 0%
- Update embedded widgets for new resolution and feature set: 0%
Ei kommentteja:
Lähetä kommentti