Webcat

Hello! Sometimes at surfing a part of the page doesn't display (only white background). To make the page displayed need to refresh the page, or TO OPEN BOOKMARKS AND GO BACK TO THE PAGE. How to fix this problem?

Well, on the technical side, the result of spending a good part of this weekend with testing is:
The HTML5 compatibility has regressed in your QtWebKit build v5.212.0-10.43.1.jolla compared to v5.6.2+git3-1.19.1 from Jolla by "-18 points" in the area of "Storage" providers and by "-1 point" in "Performance: Shared workers", according to HTML5test.com.
But the improvements are vast and impressive: An increase in the cumulative HTML5test score by 75 "points" (329 - 292 + 18 + 20, trying to take the "cheating" of Webcat 2.9-1 in the areas HTML5-Audio and -Video into account), so with "-19 points" due to aforementioned regressions, other HTML5 features were improved "by 94 points". BTW, both QtWebKit5 based web browsers for SFOS, Webcat 2.9.7-1 and the last (now unmaintained) WebPirate 2.1-3, score "329 points" with your QtWebKit 5.212.0-10.43.1 on my two Jolla 1 phones; note, that you reported "326 points", so if this has not been a typo, there is something (positively) different on my devices.
Much more importantly though, is the impact in practice: Finally I tested a couple of web pages which used to fail with Jolla's latest QtWebKit 5.6.2 build, e.g. EFF's Panopticlick: They now work well with your QtWebKit 5.212.0-10.43.1 (as with the Gecko based Jolla Browser or Firefox for Android under AlienDalvik), and specifically Webcat scores quite well on Panopticlick (in contrast to WebPirate, so here your browser makes a significant difference!).

But the big take away is IMO:
Manually downloading and installing the five RPMs is not really a feasible way to distribute QtWebKit 5.212, and keeping it up to date implies regularly visiting your Mer-OBS repository. Although I tried to be more cautious than you suggested by using pkcon install-local *webkit*.rpm, I once accidentally downloaded one out of the five RPMs at v5.6.2-10.90.1.jolla (just "mis-tapped" a single line lower or higher in the directory listing), creating a version mismatch after installing all five RPMs, which caused Webcat to crash on startup; it took a while until I had analysed this and ultimately understood what went wrong (while many may have given up in this situation). And anybody not reading your instructions carefully will download and install the newest and highest numbered RPMs available there, as I initially did.
Hence my suggestion is:
Please create two qtwebkit5-V-R.jolla.*.rpm ("V" is currently "5.212.0" and "R" "10.43.1") "meta-RPMs" for armv7hl and i486 (if "qtwebkit5" does not collide with any existing package name, otherwise pick some other name, e.g. "webkit5"), which contain nothing but dependencies on the five RPMs libqtwebkit5 libqtwebkit5-widgets qt5-qtqml-import-webkitplugin qt5-qtqml-import-webkitplugin-experimental qt5-qtwebkit-uiprocess-launcher in exactly (i.e. Requires: P = V-R in the RPM spec) their corresponding version. Then upload these six RPMs to your repository on Openrepos. Finally create a new Webcat RPM, which depends on the meta-RPM, requiring at least version 5.212.0 (i.e. Requires: qtwebkit5 >= 5.212.0) for i486 and armv7hl. This scheme (introducing one level of indirection) allows you to update QtWebKit independently of Webcat and vice versa, and easily switch to using an updated QtWebKit5 when finally distributed by Jolla, simply by updating the "meta-RPM".
As you stated, that you are expecting Jolla to integrate QtWebKit >= 5.212.0 in SFOS 2.1.4 or 2.1.5, this will take 5 to 10 months (if Jolla maintains their current release cadence), so IMHO it is definitely worth to effort, in order to provide users with an easily installable, well working and vastly improved Webcat-"experience" until then.

As you may have already derived from the increasing amount of lengthy postings here (not just mine ;) ), there are many former WebPirate users looking for an alternative (to the Jolla Browser), native web browser:
And there is only one, your Webcat!

While I was primarily keen on having the revived QtWebKit5 available for SailfishOS (thanks again for pursuing this) for security issues and other bugs fixes, I was also curious about functional improvements QtWebKit 5.212.0 brings over v5.6.2+git3.
Comparing the results of HTML5test.com of Webcat 2.9.7-1 and QtWebKit 5.212.0-10.64.1 with Webcat 2.9-1 and QtWebKit 5.6.2+git3-1.19.1, there are indeed a couple of improvements, but actually the final score is lower (276 of 555 points, down from 292 points), as some HTML5 functionality has seemingly regressed:

• Performance: Shared workers
• Video: 0 points (!), down from 20 of 33
• Audio: 0 points (!), down from 18 of 30
• Storage: 15 points, down from 33 (!) of 35

The seemingly lacking support for HTML5 audio and video makes me wonder, if these regressions are really caused by QtWebKit 5.212.0 in general or if they are specific to you build 5.212.0-10.64.1.jolla?

I've tried to install QtWebkit from leszek repository, but this error is showed:
Error fatal: There is no update candidate for libqtwebkit5-5.6.2+git3-1.18.1

As the recent Webcat update (to v2.9.7-1) has a couple of workarounds for the outdated QtWebKit 5.6.2 (SailfishOS currently still provides) removed (see Webcat's changelog), and I appreciate leszek's push for replacing it with the revived QtWebKit5 very much, I opted for installing the recent build of it from leszek's Mer-OBS.
This turned out to work well, but took a while for me to figure out how to do that properly, hence I am documenting these steps here to save other people's time.

Edit: Do not carry out the steps below! Rather perform everything manually with leszek's RPMs v5.212.0-10.43.1, as described in his first reply to this post.
Although using Mer-OBS repositories directly is supposed to make downloading, installing and updating RPMs much easier, this seems to be slightly broken under SailfishOS, resulting in "it almost works, but not really"; a state, in which one can spend hours on debugging, only to ultimately conclude that this is fundamentally flawed, and not one's failure to use it correctly (you may gain some background knowledge and experience with zypper, OBS and pkcon, though ;\ ).

1. Adding leszek's Mer-OBS repository
As adding a repository is deliberately impossible per pkcon, install zypper to perform this step:
[nemo@sailfish]$ pkcon install zypper
Then use it to add leszek's Mer-OBS repository:
[nemo@sailfish]$ devel-su
[root@sailfish]# zypper ar -c http://repo.merproject.org/obs/home:/leszek/sailfish_latest_armv7hl/home:leszek.repo
Note that, for x86-devices (e.g. Jolla Tablet), you have to use instead: zypper ar -c http://repo.merproject.org/obs/home:/leszek/sailfishos_latest_latest_i486/home:leszek.repo
To check, that this went well, use zypper lr and look for the repository named home_leszek.
If this has been successful, hit Ctrl-d (or type exit) to close the root shell and become the regular user nemo, again.

2. Upgrade QtWebKit5:
First you must execute (which takes a while):
[nemo@sailfish]$ pkcon refresh
You will be interactively asked to accept lesek's signing key, which is necessary to proceed.
If you want to check the versions of the installed QtWebKit5 RPM-packages before upgrading, do pkcon search name webkit (they all ought to be at SailfishOS's last Webkit version: v5.6.2+git3-1.19.1).
Then perform the upgrade proper:
[nemo@sailfish]$ pkcon update libqtwebkit5 libqtwebkit5-widgets qt5-qtqml-import-webkitplugin qt5-qtqml-import-webkitplugin-experimental qt5-qtwebkit-uiprocess-launcher
If you get a Fatal error: File './*/*.rpm' not found on medium 'http://repo.merproject.org/obs/home:/leszek/sailfish_latest_*/', repeat the pkcon refresh
To ensure that all these packages were successfully updated to leszek's current builds (v5.212.0-*), take a close look at the output, and / or use pkcon search name webkit, again. If a package is missing (which should not be the case, when Webcat is already installed), simply do pkcon install libqtwebkit5 libqtwebkit5-widgets qt5-qtqml-import-webkitplugin qt5-qtqml-import-webkitplugin-experimental qt5-qtwebkit-uiprocess-launcher (nothing will happen for already installed packages).

3. In order to check for updates of QtWebKit5 (no matter, if from leszek or Jolla) at any (later) time, and to download and install them (when there are any updated versions), just execute these two command lines (again):
[nemo@sailfish]$ pkcon refresh
[nemo@sailfish]$ pkcon update libqtwebkit5 libqtwebkit5-widgets qt5-qtqml-import-webkitplugin qt5-qtqml-import-webkitplugin-experimental qt5-qtwebkit-uiprocess-launcher

4. If you want to delete your subscription of leszek's Mer-OBS repository on your device (e.g. when Jolla starts distributing QtWebKit 5.212 or newer), simply execute
[root@sailfish]# zypper rr home_leszek

@leszek: Is this the route you envisioned for users to upgrade QtWebKit?
BTW, can you please briefly explain the difference between your RPMs qt5-qtqml-import-webkitplugin and qt5-qtqml-import-webkitplugin-experimental, e.g what experimental features the latter contains?

Thank you so much for your efforts!

When you will add Polish translation? It's ready on transifex.

Thanks for the update and your continued efforts for making this browser powerful, it's greatly appreciated.

Two questions/requests:

- I am using Mailpile as a secure and fully encrypted e-mail client, it runs on my server and is accessible via webmail. It works great on Sailfish Browser and Brave (Android), but somehow scrolling is broken with Webcat (and Webpirate), either with mobile or desktop user agents/respective UIs. Since it works fine with Sailfish Browser, it means the issue is not with Mailpile UI nor Sailfish gestures, so there is hope. Could you please have a look and tell me if a fix would be possible? I suppose other websites could fail as well. Here is a demo of Mailpile where you can see the issue: https://demo.mailpile.is/in/inbox/ and see Sailfish Browser working as expected.

- Would it be possible to add a "Close current tab" in the extra toolbar? It would be great to be able to close current tab with just one click and without going to the tab view. Even better would be to allow custom actions (close current tab, for instance) for long press on the menu button that shows the extra toolbar. Currently it only has a shortpress action. Webpirate had this feature with a custom button with user-defined shortpress and longpress actions. I was using New tab/Close tab as actions and used this button all the tlme, but now Webpirate is long dead.

- And one last thing because I announced two but can't stop: why not moving the Favorite toggle button to the extra toolbar? It's a button that is typically seldom used because users set their favorites only once even if they visit them often, they don't need to be toggled often. It eats significant space in the main toolbar and in fact I often missclick on it. I would be happy to free some space for the URL bar by moving it to the extra toolbar, or even better to leave space for a new "Custom" button with user-defined shortpress and longpress actions (the Webpirate code on Github would certainly help)!

Thanks in advance for your answer, keep up the great work on the best Sailfish browser (and video player).