Deprecation notice: SilicaWebView, QtWebKit

First thanks for the new Sailfish WebView API. To make it a little more better here some of my experience with the new API. I added Sailfish WebView API as second machine to my browser app Ielig:Web last year in october.

  1. The new API is much better for all the new trendy features
  2. As in the example above in most case the text will presented enhanced but it is impossible to zoom out more then the starting size
  3. The Sailfish WebView API crashed randomly. This can happen direct with starting an url or some minutes later. In most case I can read some web pages before the crash. Crashes happens also when using the native mail client (using the same API?).
  4. I am not sure that there no remains in browser data after surfing e.g. this forum in the API private mode. To handle with this my app I will first delete the browser data directoy and then start an new session. There must be a better way. Can I now trust the private mode? Is there complete declaration of data stored after using the API?
  5. When switching javascript off (and this is my default setting) in the old API I can catch every embedded external url in a web page. The new API has also a signal which sounds like the signal in the old API for doing the trick. But in my test the new signal sleeps sometimes. Is there a new status?
    https://forum.sailfishos.org/t/sailfish-webview-signal-linkclicked-sleeps-sometimes/9189

I have some more nice-to-have ideas but the new API is great - when stable. Many thanks.

3 Likes