Closed ghost closed 6 years ago
Pixel Ratio is something you need to set for every device differently. So the Pixel Ratio is set through a hack as Jolla refuses to set a global default Pixel Ratio for their Qt Platform (its always 1.0). The user agent might only affect the pixel ratio implicitly when set to a desktop browser for example which tries loading the desktop page instead of the mobile one. m.google.com is broken for me does basically nothing other then showing me a endless progressbar. This is consistent with google plus being broken or not working at all and news.google.com
WebPirate JS Code? Can you explain what you mean? Which exactly?
Basically i try to say is to use the webpirate code (if possible) to solve the rendering problems of some pages (mentioned above). this in order to improve webcat.
I speaking of webpirate in this thread because they have been brothers. : ) Make wc great llelectronics YouCan!
Ok figured out the issue I guess. It was no JS code that WebPirate had (we usually shared them anyway as soon as we found some cool new hack). It was pretty much that I broke it by adding clever code that catches on website loading if the cursor is set in a input or textbox to automatically show the keyboard. I somehow (had to be drunk there is no other explanation) thought it was a good idea to overwrite the whole window.onload javascript function instead of just adding the code necessary for the text input detection. Anyways fixed now with https://github.com/llelectronics/webcat/commit/a4342c7d8cb91137ced35333dca6579c6a259ffd
Tons of thanks.. i will try now...
Yes fixed : ) Now wc feeling more smooth Antutu-Html5-Test: PASS
Acid3-Test: PASS
Also maemo-talk layout almost fixed with a4342c7 by updating same thread, to look the fix.
Maemo Talk Layout can only be fixed I guess by putting it in the blacklist for the DevicePixelRatio. Or they ultimatively add a mobile theme to their site :P Anyways worked on integrating the rest of the Jolla/Mer patches into the QtWebkit package. Also tweaked a little bit on smoothness here and there and the Device Pixel Ratio Hack should work a tiny bit better now. The QtWebkit 5.212 package should be also now fully compatible with Jolla Settings.
wow ; thx ; I wil try now.
It is still building though
Edit: Sailfish port to sony xperia x.
Uff you already have the Sailfish X Image? Hmm... I don't have that yet.
: ) yeah. i am searching the link to send to you...
No hurry. I can still wait. After seeing the irc logs it isn't really ready anyways.
https://mega.nz/#F!BfpxWJxY!Q0RN21U7AJeg-quaJqC2cQ It is for testing, But i can not wait more llelectronics.
calls work , and much more...
It is already updated qtwebkit in obs? because look not updated.
Still building. Takes its time
Ok.. take you time.
I has been installed the new qtwebkit. Work much much much better, thx = ) [ cursor point ] > fixed.
i installed Sailfish X or (xperia x ; port(aarch64) yesterday, i tried to install qtwebkit with webcat, but i was expecting the architecture incompatibility error. Just notifying...
For the architecture issue see this post: https://sailfishos.org/wiki/Sailfish_X_Build_and_Flash At the end they mentioned to use rpm -ivh instead of pkcon install-local as root.
AHH! Thank you; will try. Are you already using sony xperia x with SFOS image? I will test the new WC release on some changes in user-agent, to check if facebook work.
Also a Sailfifh-podcast: On how install the new qtwebkit-engine to use with the new version of Wecat 2.9.7 will much needed for end-users, they could confuse, or not knowing how to install the correct packages of new Qtwebkit-engine
It is not meant for end users yet. I really hope that Jolla will include qtwebkit officially in 2.1.4 or 2.1.5
Okay; Jolla has to accept your great work that you have done, s o o n e r. Thanks for ur nice work...
#########################Area Sony Xperia X######################
I get install all the new Qtwebkit5.212 + Webcat with success.
[root@Sailfish full-qtwebkit5.212]# rpm -ivh .rpm Preparing... ########################################### [100%] file /usr/lib/libQt5WebKitWidgets.so.5 from install of libqtwebkit5-widgets-5.212.0-10.43.1.jolla.armv7hl conflicts with file from package libqtwebkit5-widgets-5.6.2+git3-1.19.1.armv7hl file /usr/lib/qt5/libexec/QtWebProcess from install of qt5-qtwebkit-uiprocess-launcher-5.212.0-10.43.1.jolla.armv7hl conflicts with file from package qt5-qtwebkit-uiprocess-launcher-5.6.2+git3-1.19.1.armv7hl file /usr/lib/libQt5WebKit.so.5 from install of libqtwebkit5-5.212.0-10.43.1.jolla.armv7hl conflicts with file from package libqtwebkit5-5.6.2+git3-1.19.1.armv7hl file /usr/lib/qt5/qml/QtWebKit/libqmlwebkitplugin.so from install of qt5-qtqml-import-webkitplugin-5.212.0-10.43.1.jolla.armv7hl conflicts with file from package qt5-qtqml-import-webkitplugin-5.6.2+git3-1.19.1.armv7hl file /usr/lib/qt5/qml/QtWebKit/experimental/libqmlwebkitexperimentalplugin.so from install of qt5-qtqml-import-webkitplugin-experimental-5.212.0-10.43.1.jolla.armv7hl conflicts with file from package qt5-qtqml-import-webkitplugin-experimental-5.6.2+git3-1.19.1.armv7hl [root@Sailfish full-qtwebkit5.212]# rpm -ivh .rpm -f Preparing... ########################################### [100%] file /usr/lib/libQt5WebKitWidgets.so.5 from install of libqtwebkit5-widgets-5.212.0-10.43.1.jolla.armv7hl conflicts with file from package libqtwebkit5-widgets-5.6.2+git3-1.19.1.armv7hl file /usr/lib/qt5/libexec/QtWebProcess from install of qt5-qtwebkit-uiprocess-launcher-5.212.0-10.43.1.jolla.armv7hl conflicts with file from package qt5-qtwebkit-uiprocess-launcher-5.6.2+git3-1.19.1.armv7hl file /usr/lib/libQt5WebKit.so.5 from install of libqtwebkit5-5.212.0-10.43.1.jolla.armv7hl conflicts with file from package libqtwebkit5-5.6.2+git3-1.19.1.armv7hl file /usr/lib/qt5/qml/QtWebKit/libqmlwebkitplugin.so from install of qt5-qtqml-import-webkitplugin-5.212.0-10.43.1.jolla.armv7hl conflicts with file from package qt5-qtqml-import-webkitplugin-5.6.2+git3-1.19.1.armv7hl file /usr/lib/qt5/qml/QtWebKit/experimental/libqmlwebkitexperimentalplugin.so from install of qt5-qtqml-import-webkitplugin-experimental-5.212.0-10.43.1.jolla.armv7hl conflicts with file from package qt5-qtqml-import-webkitplugin-experimental-5.6.2+git3-1.19.1.armv7hl
[root@Sailfish full-qtwebkit5.212]# rpm -ivh *.rpm --force Preparing... ########################################### [100%] 1:qt5-qtwebkit-debugsourc########################################### [ 17%] 2:libqtwebkit5-widgets ########################################### [ 33%] 3:qt5-qtwebkit-uiprocess-########################################### [ 50%] 4:libqtwebkit5 ########################################### [ 67%] 5:qt5-qtqml-import-webkit########################################### [ 83%] 6:qt5-qtqml-import-webkit########################################### [100%]
[root@Sailfish Documents]# rpm -ivh harbour-webcat-2.9.12-1.armv7hl.rpm Preparing... ########################################### [100%] 1:harbour-webcat ########################################### [100%]
But Webcat run choppy,not smooth Just reporting to [ Webcat Database ]
Hello Lesner Do you know if qtwebkit5.212 was accepted by jollla?
Just take a look here: https://git.merproject.org/mer-core/qtwebkit5/merge_requests/12 I don't see any progress there.
OK I am totally disappointed with Jolla they never listen to the developers tremendous mistake of them because the developers are a super important part in this case for sailfish OS. Sony xperia x is a disaster right now too <> Webcat is unusable
You need to talk to them directly by using the mer-meetings to get their attention. Otherwise the threads in together.jolla.com might be not seen or stuff postponed in urgency. So the last time I asked about QtWebkit they said they'll take a look into it and the TJC thread got a tracked by Jolla logo so I guess someone is taking a look into it fixing it.
The problem with Jolla that it is a lot smaller company than it used to be. So getting this done is a lot harder especially if they don't only have to listen to users feedback but also have to create stuff for their customers and shareholders.
yeap, key-true-developers for sailfish OS are not already in jolla as Mohammed Sameer - Marc Dillon - Rakko Rapola
Hello Lesner I see not progress on qtwebkit5212, it will be because you have a label of WIP ? They still working on out date qtwebkit5.6 and pushing to qtwebkit5.6.4-on-mer-core.
I am not sure whats going on. I did not hear back from them at all. So I will leave everything as is for now. Jolla has not enough devs to maintain qtqwebkit as it seems. They aren't even able to keep gecko up to date.
Yes Gecko it is outdate too. I love SailfishOS but Jolla is stress me a lot.. I do not understand why spend time or money on blockchain or something like that when the main sf-browser is causing pain to us. Anyway thanks Lesner for your nice work-on-SFOS
Hi Lesner Confirmed SailfishOS 3.0 will come with Qt5.9-WebEngine. So what is the future of webcat?
Oh you did confirm that in Barcelona? That would be nice. Not sure what the future of webcat then is. Webengine needs a redesigned browser and some features might get lost along the way.
Meanwhile I am working on an further upgraded Qt 5.212 release which I am still testing various tests with especially the Xperia X as it has some real struggles with qtwebkit for whatever reasons.
Yeap in Barcelona. Share your build of qtwebkit5212
As always the newest builds can be found here: https://build.merproject.org/package/show/home:leszek/qtwebkit5212-wHtml5Audio+Video
Only the html5 enabled is available for now.
I installed in jolla c, but not work. blank screen. Is this only xperia x? I first installed in jolla c .
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On 27 February 2018 8:24 AM, Leszek Lesner notifications@github.com wrote:
As always the newest builds can be found here: https://build.merproject.org/package/show/home:leszek/qtwebkit5212-wHtml5Audio+Video
Only the html5 enabled is available for now.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or mute the thread.
I am trying to fix issues with the Xperia X stutter that's why the current builds are broken.
Success: See my updated thread on tjc. Also added a openrepos repo for qtwebkit 5.212 https://together.jolla.com/question/171114/xperia-xbug-qtwebkit-unusably-slow/?answer=180404#post-id-180404
Wow thanks Leszek you are awesome. We need Leszek in Jolla-Team.
Hello Hero-Dev
qtwebkit5212 on openrepos is down. Any reason?
Leszek I have a big issue in all my device I can not upgrade to 2.1.4.14 via GUI. so I think that this issues is because I download the 2.1.4.14 before install original qtwebkir5.212[perhpas] , soo the solutions I think is reset the downloaded 2.1.4.14 but I do not know how? So I want to go in the folder into the system where is downloaded the 2.1.4.14 then to delete manual, then download again the 2.1.4.xxx. I think this will fix my problem. So do you know where is the folder into the system Leszek? I searched but unsucess.
Moved to a different repo: https://openrepos.net/content/llelectronicsdev/qtwebkit-5212-dev
As for the upgrade issue. Yeah this happens with my packages. You need to install the original qtwebkit packages. See Together.Jolla.com and the Openrepos instructions.
...with install the original qtwebkit packages it is not fix upgrade issue if is already downloaded the image. So I Think is fix by deteleting manually the image then download again with original qtwebkit. I do not find the folder
That has nothing to do with it. Actually if you have the original qtwebkit packages installed and it is still failing to upgrade then you might have another package causing the conflict. Take a look at the log in /var/log/systemupdate.log and see if you can find any hints. The update is not downloading an image but the packages to upgrade to. The upgrade process when restarting and showing the minimal ui (minui) with the progressbar is actually the process of installing those rpm files. When it fails it usually means there is some kind of conflict.
thanks Leszek it is appreciable I will check now, it is strage because is my first time with this issue in all my devices.
Hi llectronics. i am testing WC-v2.9.7 with patched Qtwebkit,. Then i have some report . .