Webcat

Rating: 
4.6
Your rating: None Average: 4.6 (30 votes)

A simple webbrowser which allows viewing webpages and surfing sites.
It is based upon the webkit engine provided by Qt5.

Current features include:

  • Landscape support
  • Tabbing support (real without reloading of tabs)
  • Bookmark support
  • Setting browser user agent
  • Setting default font sizes
  • Opening up links in new tab (by long press and hold on link)
  • Copy links (by long press and hold on link)
  • Open media links with internal or external viewer (e.g. LLs VideoPlayer)
  • Setting DNS Prefetch
  • Setting Offline WebApplication Cache
  • Manually add bookmark with specific user agent
  • Fast scroll to top or bottom of page
  • Watch Youtube with internal or external player (e.g. LLs VideoPlayer) with direct link
  • Download Youtube videos in different formats
  • Private Browsing
  • Clear Cache, Cookies, History
  • Page search functionality
  • Simple adblocking (simple rules no bloat)
  • Integrated file manager (with cut, copy, paste, creating folders, permission changes, renaming files)
  • Integrated Download Manager
  • Keyboard Hotkeys (for TOHKBD or bluetooth keyboards)
  • Support different screen resolutions (support for Nexus4, Nexus 5, Nexus 7)
  • Allow setting as default browser
  • Backup Manager (Import/Export Bookmarks,Cookies,History,Settings)
  • Proxy Support

Video demonstration: http://youtu.be/1uVjaETqmMA

0.9 Video demo: http://youtu.be/nNYjdr5tCSs

2.0 Video demo: http://youtu.be/WZXlqOrLKK8

2.0.9 Video demo: https://youtu.be/Ck2TND0-PwE

2.1.0 Video demo Backup Manager: https://youtu.be/sBge7JAlXro

Sourcecode: https://github.com/llelectronics/webcat

From Version 2.9.7 on it is recommend to use QtWebkit 5.212 in combination with Webcat. You can get builds from here: https://openrepos.net/content/llelectronicsdev/qtwebkit-5212-dev

Donations via PayPal

Screenshots: 
Application versions: 
AttachmentSize
File harbour-webcat-0.8-2.armv7hl.rpm58.49 KB
File harbour-webcat-0.8-3.armv7hl.rpm64.67 KB
File harbour-webcat-0.8-4.armv7hl.rpm79.63 KB
File harbour-webcat-0.8-5.armv7hl.rpm79.65 KB
File harbour-webcat-0.9-1.armv7hl.rpm92.09 KB
File harbour-webcat-0.9-2.armv7hl.rpm92.05 KB
File harbour-webcat-0.9-3.armv7hl.rpm92.25 KB
File harbour-webcat-0.9-4.armv7hl.rpm99.62 KB
File harbour-webcat-0.9.6-1.armv7hl.rpm123.05 KB
File harbour-webcat-0.9.7-1.armv7hl.rpm123.69 KB
File harbour-webcat-0.9.8-1.armv7hl.rpm125.66 KB
File harbour-webcat-0.9.9-1.armv7hl.rpm134.53 KB
File harbour-webcat-0.9.9-2.armv7hl.rpm134.54 KB
File harbour-webcat-1.0.0-1.armv7hl.rpm139.59 KB
File harbour-webcat-1.0.1-1.armv7hl.rpm139.88 KB
File harbour-webcat-1.0.2-1.armv7hl.rpm140.2 KB
File harbour-webcat-1.9.9-1.armv7hl.rpm190.17 KB
File harbour-webcat-1.9.9-2.armv7hl.rpm156 KB
File harbour-webcat-2.0.0-1.armv7hl.rpm156.18 KB
File harbour-webcat-2.0.1-1.armv7hl.rpm156.27 KB
File harbour-webcat-2.0.2-1.armv7hl.rpm156.52 KB
File harbour-webcat-2.0.3-1.armv7hl.rpm156.52 KB
File harbour-webcat-2.0.5-1.armv7hl.rpm167.81 KB
File harbour-webcat-2.0.5-2.armv7hl.rpm167.66 KB
File harbour-webcat-2.0.7-1.armv7hl.rpm168.48 KB
File harbour-webcat-2.0.8-1.armv7hl.rpm177.98 KB
File harbour-webcat-2.0.9-1.armv7hl.rpm182.34 KB
File harbour-webcat-2.0.9-2.armv7hl.rpm182.42 KB
File harbour-webcat-2.1.0-1.armv7hl.rpm195.54 KB
File harbour-webcat-2.1.0-1.i486.rpm206.11 KB
File harbour-webcat-2.2.0-1.armv7hl.rpm202.02 KB
File harbour-webcat-2.2.0-1.i486.rpm212.92 KB
File harbour-webcat-2.2.1-1.armv7hl.rpm217.84 KB
File harbour-webcat-2.2.1-1.i486.rpm228.56 KB
File harbour-webcat-2.2.2-1.armv7hl.rpm218.97 KB
File harbour-webcat-2.2.2-1.i486.rpm229.58 KB
File harbour-webcat-2.3-1.armv7hl.rpm224.99 KB
File harbour-webcat-2.3-1.i486.rpm240.86 KB
File harbour-webcat-2.4-1.armv7hl.rpm230.41 KB
File harbour-webcat-2.4-1.i486.rpm242.32 KB
File harbour-webcat-2.5-1.armv7hl.rpm234.54 KB
File harbour-webcat-2.5-1.i486.rpm246.44 KB
File harbour-webcat-2.6-1.armv7hl.rpm234.73 KB
File harbour-webcat-2.6-1.i486.rpm246.42 KB
File harbour-webcat-2.7-1.armv7hl.rpm238.34 KB
File harbour-webcat-2.7-1.i486.rpm249.41 KB
File harbour-webcat-2.8-1.armv7hl.rpm267 KB
File harbour-webcat-2.8-1.i486.rpm283.6 KB
File harbour-webcat-2.9-1.armv7hl.rpm269.12 KB
File harbour-webcat-2.9-1.i486.rpm284.82 KB
File harbour-webcat-2.9.7-1.armv7hl.rpm302.86 KB
File harbour-webcat-2.9.7-1.i486.rpm318.92 KB
File harbour-webcat-2.9.8-1.armv7hl.rpm310.98 KB
File harbour-webcat-2.9.8-1.i486.rpm325.56 KB
File harbour-webcat-3.0.0-1.i486.rpm359.59 KB
File harbour-webcat-3.0.0-1.armv7hl.rpm344.45 KB
File harbour-webcat-3.0.1-1.i486.rpm360.65 KB
File harbour-webcat-3.0.1-1.armv7hl.rpm345.07 KB
File harbour-webcat-3.0.2-1.i486.rpm361.7 KB
File harbour-webcat-3.0.2-1.armv7hl.rpm345.72 KB
Changelog: 
  • Make quickscroll area smaller, appear after bigger threshold, and don't react on pressed
  • fine tune extraThreshold for landscape quickscroll
  • Disable some debug output
  • Fixed moving of files (causing loss of data) in filemanager
  • Fixed filepicker not able to select files
  • Faster tab switching
  • Don't loose keyboard shortcuts on tab switch / creating new Tab
  • Add function to get nextTab and prevTab
  • Added shortcut for quick tab switching ctrl+tab & ctrl+shift+tab
  • hide tabBar and bookmarkList before switching tab
  • Open Filemanager immediate and don't perform animation when entering about:file
  • Add more keyboard shortcuts (Ctrl+W - Close, Ctrl+T - New Tab, Ctrl+N - New Window, Escape - Stop)
  • Allow swiping on urlTitle (only visible after website loaded completely) to switch tabs
  • Use threshold value resolution dependent for back/forward swipes on minimized toolbar
  • Fix highlighted tab not filling whole width with highlight

Comments

llelectronics's picture

See my comment about this. 

Don't use the repository download the files directly and install them manually. 

carmenfdezb's picture

Ok, sorry, I didn't see your comment. I've followed your instructions and now it works. Thank you!!

olf's picture

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!

llelectronics's picture

It is is not recommend by me currently to do it this way. (e.g. adding the repo) 

Instead I would recommend installing the rpms manually as mer obs somehow managed to automatically give some older packages higher version numbers. 

So you need version 5.212.0-10.43.1 currently as this is the newest version. See the dates in the repo url: http://repo.merproject.org/obs/home:/leszek/sailfish_latest_armv7hl/armv...

So download the rpms : 

  • libqtwebkit5-5.212.0-10.43.1.jolla.{armv7hl/i486}.rpm
  • libqtwebkit5-widgets-5.212.0-10.43.1.jolla.{armv7hl/i486}.rpm
  • qt5-qtqml-import-webkitplugin-5.212.0-10.43.1.jolla.{armv7hl/i486}.rpm
  • qt5-qtqml-import-webkitplugin-experimental-5.212.0-10.43.1.jolla.{armv7hl/i486}.rpm
  • qt5-qtwebkit-uiprocess-launcher-5.212.0-10.43.1.jolla.{armv7hl/i486}.rpm

save them into a folder on your device. 

Then either ssh into your device or open up the terminal and cd into the folder where the rpms are stored and install the rpms with pkcon install-local *.rpm

It will ask you if you really want to install and you hit y then. 

I really hope these instructions are clear for all who have the knowledge. 
If it sounds like black magic to you just be patient and wait until Jolla maybe includes QtWebkit 5.212 in SailfishOS 2.1.4 or 2.1.5 

 

Regarding qt5-qtqml-import-webkitplugin-experimental this is a normal package containing the QtWebkit Experimental features. There is nothing really new in here compared to the previous versions. 

olf's picture

Thanks for the clarification WRT qt5-qtqml-import-webkitplugin-experimental.

Still I do not really comprehend, why you advise to not using your repository as such, but instead suggest to manually download your RPMs from it with a web browser. As the resources at Jolla are limited, I expect the integration of QtWebKit 5.212 to take a while, and have not yet seen a clear commitment from them to really do that (reading the "community collaboration meeting" log, where you asked them to).
So, while enabling your repo is a bit more work once, installing those packages and keeping them up to date, when you built new versions (e.g. 2017-09-23), is much easier and far less error prone with pkcon (IMO), than manually looking them up / checking if they are updated in a web browser, downloading each of the five RPMs manually, and finally installing them manually one by one.

olf's picture

Oh, the 2017-09-23 update of the metadata for your Mer-OBS repository seems to be broken: A pkcon refresh now always results in Fatal error: [home_leszek|] Repository not found.
The trailing pipe character ("|") is apparently new and supposedly the reason. So now everybody is now forced to perform downloading, installing and checking for updates of your QtWebKit packages manually.

I wonder, why I was unable to locate the pipe character in any of the metadata files (a fgrep "|" *.xml on the gunzip'ed metadata files, repomd.xml and home:leszek.repo yields nothing).

Can you please fix that, so one has a choice how to obtain and maintain your QtWebKit5 builds, again.

llelectronics's picture

I did not change anything so not sure whats going on here. 

This is maybe another reason not to use the repository directly but download the rpms manually. 

The other is that the higher version number does not correspondent with the latest version. As stated above the newest html5 audio + video enabled version is: 10.43.1

atlochowski's picture

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

llelectronics's picture

uff did miss that one. Will add this in next release and import it soon to github.

Kabouik's picture

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).

llelectronics's picture

... but somehow scrolling is broken with Webcat (and Webpirate), either with mobile or desktop user agents/respective UIs ...

Interesting. Only noticed that problem on Google+ (that you can make run if you don't access the plus.google.com page but a subpage instead). I think this is limitation of the qtwebkit engine. Maybe I can find a workaround but my hopes are not very high on fixing that. 

 Would it be possible to add a "Close current tab" in the extra toolbar?

The extra toolbar is cramped up already and basically full already. But I think the reload button there could be removed as it is already active as soon as you press on the urlbar itself. Also the reload function for quick access seems not very often used. Close Tab instead is one thing used more often. Btw. if you don't know it yet. You can reach any extratoolbar item and quickswitch between tabs by pressing and holding the goto / tab button (bottom left) and then just like the pulley menu but horizontaly mark the items in the extra toolbar menu and let go on the item you want to activate. 
This works quite fine on the Jolla 1. Sadly the newest SailfishOS updates made it almost impossible to use on the Jolla C or Jolla Tablet as it interferes with the newer bigger swipe to minimize or open app drawer actions. 

- And one last thing because I announced two but can't stop: why not moving the Favorite toggle button to the extra toolbar? 

As I said the extra toolbar is already cramped up. But I think I could move the favorite option next to the reload button when focus is on the urlbar. That makes the most sense I guess and should be easily found by the users aswell. 

Thanks for your comment and suggestions on improving the browser. 

Kabouik's picture

I think this is limitation of the qtwebkit engine. Maybe I can find a workaround but my hopes are not very high on fixing that.
Hope you'll find a way, thanks for trying anyway even if so far only Google+ seemed to exhibit the same issue.

The extra toolbar is cramped up already and basically full already.
It depends on the device you are using. On Jolla C, there is still room for one icon in portrait mode, and more icons than necessary in landscape mode. Note that it could also use the same mechanism as in Webpirate, i.e., an horizontally scrollable bar (is it tricky to mix features from Web Pirate source code in Webcat?), which would solve the issue in smaller devices. Most Android phones being ported to Sailfish by the community are also about the size of the Jolla C, or even bigger for the latest models, as are the Jolla and Youyota tablets, or the - hopefully - future keyboard phone from Chen.

Closing tabs without going to the tab view would really be useful: there are a lot of links that you just click on and they open a new tab, you read these new tabs a little and then just want to close them to go back to the origin website. Think of Wikipedia and it's billion of links that no one can resist clicking when reading an article for instance. This is especially true as the animation to show and hide the tab list in Webcat is a bit slow: it can get a bit frustrating when used repeatedly because it makes you feel you are literally waiting for it to end.

I concur with you about the Refresh icon, especially as it shows up when you touch the URL bar anyway, as you said.

The quick tab switch and access to the extra toolbar features are nice (but the latter is redundant with the right menu icon, or did I miss something?), but require some accuracy. Or instead I should say I am personally not very efficient in using them and am a lot more comfortable using the Menu icon on the right that displays the extra toolbar (but could use a secondary action on long press). Plus I'm currently using a Jolla C, and as you said it's more convenient on the original Jolla.
But I think I could move the favorite option next to the reload button when focus is on the urlbar. That makes the most sense I guess and should be easily found by the users aswell.

Yes, I think people would associate favorites with URLs anyway so it would make sense to have them together, while the extra toolbar would be more focused on being a "tool" bar (read view, split screen, lock orientation, etc.). Instead, I do think that showing an icon with two user-defined actions for short and long presses would make sense though. And if they really want it, users could choose to use "favorite" as one of these functions! But I don't think anyone would do it to be honest, which kind of supports the whole point.

One additional thing: landscape mode is often useful when using a mobile browser, and Webcat support for landscape is great overall (the split screen option is a jewel), but the Tab page is a bit akward to use in that orientation because it just splits the view horizontally between bookmarks and tabs, which makes it significantly hard to use/read when you have more than four tabs. Would it not make sense to split vertically and have one side of the screen showing bookmarks and the other the open tabs? Letting users choose sides would be great for better left- and right-handed support, but that's not critical.
By the way, I noticed that the Lock orientation does not work on Jolla C. I don't know about Jolla 1, I seem to remember it used to work correctly but that was a long time ago and I can't test properly now as my Jolla 1 is not updated to the latest Sailfish version.

Also, since I mentioned Web Pirate above, and I know that you have helped Dax on some features like setting default browser, there is another unique feature in Web Pirate that is absolutely fantastic: the experimental Sailfish text input for text fields. It solves issues, basically. This long post could not be edited in Webcat because you cannot navigate through a web text field without arrow keys, nor can you resize it to show the whole text and click where you want. You cannot efficiently select editable text either while Sailfish input offers the Sailfish selection mechanism used in other applications, and this system also allows showing a lot more text, despute bigger default font size. You can circumvent all the text field issues with the Sailfish text input, like in Storeman or Web Pirate. Same issues occur with forum posts, blog posts, or e-mail in web clients, so this may be really important for people who use their mobile browser for writing and not only reading.

I know Webcat is not Web Pirate and I don't want to offend you by suggesting some of its features. Both have their pros and cons and I never could choose my favorite when they were both actively developped, but Web Pirate is now dead and not maintained anymore, so I'm just throwing comments in case you'll still be looking for stuff to add in your to-do list in 5 years. :>

llelectronics's picture

Note that it could also use the same mechanism as in Webpirate, i.e., an horizontally scrollable bar (is it tricky to mix features from Web Pirate source code in Webcat?)

It is a totally different codebase that also went through rewrites. Webcat on the other hand never had a major rewrite and the extra toolbar is very static and adding a scrolling element would break the quick navigation option totally.

(but could use a secondary action on long press)

I don't like to blow up the code with configurable toolbars as it would be another codepath to support with lots of potential stuff breaking. I am thinking about it though. Maybe long pressing here makes more sense and works better for the quick extra toolbar access instead of using the goto button. I will test several options here and will decide what to do then.

but the Tab page is a bit akward to use in that orientation because it just splits the view horizontally between bookmarks and tabs, which makes it significantly hard to use/read when you have more than four tabs.

This is mostly a problem on smartphones. On the tablet it does work very good. But I will test your suggestion though it needs a bit of restructuring as those (bookmarks and tabview) are in a column and that does not work with it.

By the way, I noticed that the Lock orientation does not work on Jolla C. I don't know about Jolla 1, I seem to remember it used to work correctly but that was a long time ago and I can't test properly now as my Jolla 1 is not updated to the latest Sailfish version.

Tested it here on the Jolla C and it works just like it should

About the text input never had and issue with this. Writing and reading text works just fine. Though I will take a look at potential improements

Kabouik's picture

Hey Llelectronics, thanks for the reply. 

It is a totally different codebase that also went through rewrites. Webcat on the other hand never had a major rewrite and the extra toolbar is very static and adding a scrolling element would break the quick navigation option totally.

Understood. It was worth asking though because there are so many great (and non-redundant) features in both browsers. The parallel between Web Pirate and Webcat is kind of natural because they have been the two major non-official browsers for some years now.

I don't like to blow up the code with configurable toolbars as it would be another codepath to support with lots of potential stuff breaking. I am thinking about it though. Maybe long pressing here makes more sense and works better for the quick extra toolbar access instead of using the goto button. I will test several options here and will decide what to do then.

Looking forward to seeing/testing what you'll come up with.

Tested it here on the Jolla C and it works just like it should

Weird, I tested again and it still rotates despite lock mode in mine. I suppose it may conflict with one of those "rotate everything" patches? The flavor I'm using is "Allow any rotation", which works quite well. I have a "Lock rotation" button in my Powermenu2 screen and it does lock the rotation system wide, but when in rotation-free mode (disabling this toggle in Powermenu2), I can see that the Webcat's lock has no effect.

About the text input never had and issue with this. Writing and reading text works just fine. Though I will take a look at potential improements

Surely it works for short messages, but it is not user-friendly, and bigger problems start to appear for longer messages such as these: you can't scroll the text field so if there's more text than the default field size can show, you are screwed unless you have a keyboard with arrow keys; the UI scaling is inconvenient, so are the text-selection and copy-pasting mechanisms, and you may touch a link you didn't want to activate when struggling with the zoom level and view or when placing your cursor.

My previous wall text here looks like this and cannot be edited, while it looks like this in Storeman or Web Pirate, making it not only editable, but convenient to edit (scrolling, UI is a lot more responsive, no risk of clicking on a link by mistake while trying to zoom in and move the view, Sailfish text selection mechanism, etc.). This feature is rarely seen in browsers even on Android, so I'm guessing it's not so easy, but it makes typing in a text field as easy and hassle-free as typing a SMS. It's great in my opinion.

Thanks for the git update! I will try it if I find the time before you push it to master (I have visitors at the moment so I'm rarely on the computer), but otherwise I'll be happy to test it when it hits OpenRepos. 

(Also, maybe it would be relevant to continue this discussion in the Webcat thread on TMO? Openrepos's nested view is starting to create very narrow text blocks.)

    llelectronics's picture

    Uploaded first changes like hiding the favoriticon by default and the proposed splitview in landscape mode on bookmarksmenu. All on git already if you like to test.

    skyjumper's picture

    Hi, thanks for the great app.

    Unfortunately, well actually rather often, the app locks up and needs to be killed for various sites. I use the stock browser as my alternative

    llelectronics's picture

    That is unfortunate indeed. 

    I use my app every day and don't have this problem on the sites I visit regulary. 

    The next version will have a automatic recovery if the underlying Webkit engine crashes and reloads the site then. 

    skyjumper's picture

    Hi,

    Thanks for the update. I have the issue where if I have webcat open and I try to open another link via an external app - Instagram, Twitter, the link isn't opened in Webcat. Nothing happens. I have to close and reopen webcat for it to opoen the link

    llelectronics's picture

    How did you set webcat as default browser? 

    If you use the --set-default option on harbour-webcat it should correctly set the default browser with the ability to open up links even if the browser is opened already.

    skyjumper's picture
    llelectronics's picture

    Yeah that won't work as it needs a Dbus service for such a thing to work (open application getting the request of opening a file or url).

    That's why there exists the --set-default parameter for webcat.

    skyjumper's picture

    ahah! That makes sense. So is that parameter via the command line or editing the template for the icon on the desktop ?

    Thanks

    llelectronics's picture

    It is a command line argument. You only need to run it once. It will only set the browser as default and exit immediately. 

    I had a button the settings for this but Jolla did not like it so I had to remove it from the version to get into harbour. 

    The also claimed to have something in the works for mimetypes and such though that is more than 2 years ago now :(

    skyjumper's picture

    Got it! Thanks

    Qleg's picture

    I can't login via web.skype.com. Is it possible to login or not?
     

    llelectronics's picture

    Not supported by QtWebkit. So no does not work. 

    Qleg's picture

    Thanks. but this is :-(

    olf's picture

    Maybe the maintained WebKit comes handy: [Qt-Development] QtWebKit is coming back (part 2)

    qiang1315231's picture

    Hi! Can you add www.baidu.com engine, please?

    llelectronics's picture

    Added Baidu search now on git. Should be available with the next release. 

    Pages