Konstantin Tokarev | 12 Feb 16:32 2016
Picon

New QtWebKit progress

Hi all,

I'm pleased to announce that qtwebkit-1 branch in repository [1] now contains everything needed for
successful linking of libQt5WebKit.so on Linux using gcc 4.8.4 or clang 3.7. Branch is based on today's
trunk and uses B3 compiler as a default FTL backend.

Note that QtTestBrowser is not yet here so there is nothing to run yet. Stay tuned!

Windows support is coming soon. It would be great if someone tried to compile the code on OS X (10.10 or 10.11
is required) and report encountered issues.

Also I'd like to inform you that trunk (and therefore qtwebkit-1 branch) now contains mostly working
support for MIPS architecture in JSC engine (up to DFG JIT).

[1] https://github.com/annulen/webkit

-------------

Now about sad things. There are some features that I had to disable during this work. They don't have high
priority for me, so if anything of these items is important for you, please join our project!

* QWebHistory, QWebHistoryItem, and QWebHistoryInterface. WebKit APis has changed in this field, so it
would require some investigation to restore these QtWebKit APIs.

I can assure you that I'm not going make any "official" releases without some kind of working history API,
but if you want to speed up this process your help would be welcome.

* Private browsing API was significantly changed, so it is disabled for now.

Please help if you want this feature to be implemented sooner.
(Continue reading)

Konstantin Tokarev | 20 Jan 20:42 2016
Picon

Re: Anyone here interested in QtWebKit on OS X?


20.01.2016, 19:43, "Konstantin Tokarev" <annulen <at> yandex.ru>:
> 20.01.2016, 18:33, "Coda Highland" <chighland <at> gmail.com>:
>>  On Wed, Jan 20, 2016 at 7:19 AM, Konstantin Tokarev <annulen <at> yandex.ru> wrote:
>>>   Hi all,
>>>
>>>   Is anybody here interested in QtWebKit on OS X?
>>>
>>>   Aside from ongoing project of QtWebKit reviving (which you are welcome to join in), there are
several possible improvements in QtWebKit 5.6 which could be made if you help with testing.
>>>
>>>   --
>>>   Regards,
>>>   Konstantin
>>>   _______________________________________________
>>>   webkit-qt mailing list
>>>   webkit-qt <at> lists.webkit.org
>>>   https://lists.webkit.org/mailman/listinfo/webkit-qt
>>
>>  Yes, I'm available to help with testing.
>
> 1. Could you check if https://bugs.webkit.org/show_bug.cgi?id=36853 reproduces with Qt 5?
> 2. Does modern Safari change font size on buttons when scaling page? What other modern browsers do on OS X?
> 3. Does the next HTML code display button with height 250px or something around 30px in a) modern Safari b)
other modern browsers on OS X

Forgotten to paste HTML in question:

<html><head></head><body ><button type="button" style="width:300px;height:250px;" value="bootone">botz</button></body></html>

(Continue reading)

Coda Highland | 20 Jan 18:27 2016
Picon

Re: Anyone here interested in QtWebKit on OS X?

On Wed, Jan 20, 2016 at 8:43 AM, Konstantin Tokarev <annulen <at> yandex.ru> wrote:
>
>
> 20.01.2016, 18:33, "Coda Highland" <chighland <at> gmail.com>:
>> On Wed, Jan 20, 2016 at 7:19 AM, Konstantin Tokarev <annulen <at> yandex.ru> wrote:
>>>  Hi all,
>>>
>>>  Is anybody here interested in QtWebKit on OS X?
>>>
>>>  Aside from ongoing project of QtWebKit reviving (which you are welcome to join in), there are several
possible improvements in QtWebKit 5.6 which could be made if you help with testing.
>>>
>>>  --
>>>  Regards,
>>>  Konstantin
>>>  _______________________________________________
>>>  webkit-qt mailing list
>>>  webkit-qt <at> lists.webkit.org
>>>  https://lists.webkit.org/mailman/listinfo/webkit-qt
>>
>> Yes, I'm available to help with testing.
>
> 1. Could you check if https://bugs.webkit.org/show_bug.cgi?id=36853 reproduces with Qt 5?
> 2. Does modern Safari change font size on buttons when scaling page? What other modern browsers do on OS X?
> 3. Does the next HTML code display button with height 250px or something around 30px in a) modern Safari b)
other modern browsers on OS X
> 4. Do you think if https://codereview.qt-project.org/#/c/146741 would be better to have on OS X?
>
> I guess items 2-4 are related to HIG but I'm too lazy to look it up :)
>
(Continue reading)

Konstantin Tokarev | 20 Jan 16:19 2016
Picon

Anyone here interested in QtWebKit on OS X?

Hi all,

Is anybody here interested in QtWebKit on OS X?

Aside from ongoing project of QtWebKit reviving (which you are welcome to join in), there are several
possible improvements in QtWebKit 5.6 which could be made if you help with testing.

--

-- 
Regards,
Konstantin
Konstantin Tokarev | 11 Jan 12:15 2016
Picon

QtWebKit reviving progress

Hello again,

I've created repository at https://github.com/annulen/webkit. Branch qtwebkit-1 contains Qt port of
JavaScriptCore, it can be built with build-webkit script. Resulting jsc executable successfully
passes tests.

I've added some other information to the wiki:

https://github.com/annulen/webkit/wiki

In particular, it contains list of areas where you can help in case you are interested.

Stay tuned!

--

-- 
Regards,
Konstantin
Konstantin Tokarev | 8 Jan 11:10 2016
Picon

QtWebKit + libsoup experiment

Hi all,

(reposting here from webkitnix group in case anyone from INdT team is still reading this list) 

I just re-read announcement of Nix from 2013 [1], and it mentions QtWebKit + libsoup experiment.
Were its details (goals, results, source code) published somewhere?

I'm also interested why libsoup was chosen over libcurl, and what particular drawbacks of QNAM you were
trying to overcome.

Have you done any benchmarks comparing performance of QNAM vs libsoup vs libcurl?

Thanks!

[1] https://lists.webkit.org/pipermail/webkit-dev/2013-May/024908.html

--

-- 
Regards,
Konstantin
Konstantin Tokarev | 30 Dec 13:00 2015
Picon

Reviving QtWebKit

Hello everyone,

I'd like to upgrade QtWebKit to modern WebKit code base. 

One particular goal is to obtain modern browser engine capable of running in low memory conditions on MIPS
device, which would have relatively small binary size.

I'd like to support the next configurations:

* OS: Linux (X11 and EGLFS)
* CPU architectures: x86_64, MIPS
* Compiler: g++ 4.8
* Qt >= 5.4

Other platforms may be supported on best effort basis if community is interested. 
Primary focus will probably be on WebKit2, but WebKit1 will also be supported.

In case anyone does not follow WebKit development, here are several highlights of what has changed since
last QtWebKit branch-off:

* Partial ES6 support in JavaScriptCore (https://webkit.org/blog/4054/es6-in-webkit/)
* JavaScriptCore now uses C stack
* FTL JIT - ultimate JIT tier which compiles JS using LLVM (https://webkit.org/blog/3362/introducing-the-webkit-ftl-jit/)
* JIT for CSS selectors (https://webkit.org/blog/3271/webkit-css-selector-jit-compiler/)
* MediaSource and MediaStream (WebRTC) support in GStreamer MediaPlayer implementation

Is anybody interested in this project? I'll appreciate any kinds of help.

Here are a few questions for QtWebKit developers:

(Continue reading)

Luca Carlon | 23 Nov 00:20 2015
Picon

Video to Texture

Hello,
I would like to implement video to texture in QtWebKit. I already did it for QtMultimedia and now I would like to do it in WebKit2 for Qt. The only useful doc that I could find is this: https://trac.webkit.org/wiki/QtWebKitForQt5, but it simply says what I already know. Is there any other document that you can provide or sample implementation that I could follow?
Thanks.

Luca
_______________________________________________
webkit-qt mailing list
webkit-qt <at> lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt
Allan Sandfeld Jensen | 29 Oct 10:20 2015

Re: QtWebkit JavaScript interpreter crash ( v.153112/ppc64le).

I just checked Platform.h and the usual suspects, it seems PPC64LE should be 
detected correctly and handled. Which means it should use the Cloop LLINT 
implementation for JavaScript. You could double-check if little-endian is 
correctly detected in Platform.h though. As for the page alignment, I would 
have assumed they would match ppc64 and should already work. So it could be a 
mismatch between what I tested on Debian-ppc64 and what you are using.

On Thursday 29 October 2015, Atul Sowani wrote:
> Hi Allan,
> 
> Thanks for your response! It is good to know someone who's worked on
> PPC64.
> 
> Yes, the qtwebkit did not work/compile on ppc64le. It crashes (assertion
> failure) in isPageAligned() macro. The page alignment is not correct on
> ppc64le. In addition to this, the page allocation logic and the frame
> stack functionality is not working as expected on this platform. The tried
> to modify the page alignment logic and the execution went ahead, only to
> hang in dtoa()/mult() functions in WTF. I think the page block and JS
> stack functionality needs particular attention.
> 
> As you've already worked on ppc64be, your experience of porting the code
> would be precious to me. Could you please share your experience and advise
> on how I should proceed in this task of porting the code to ppc64le?
> 
> Thanks,
> Atul.
> 
> 
> 
> 
> From:   Allan Sandfeld Jensen <kde <at> carewolf.com>
> To:     webkit-qt <at> lists.webkit.org
> Cc:     Atul Sowani/Beaverton/Contr/IBM <at> IBMUS
> Date:   10/28/2015 06:08 PM
> Subject:        Re: [webkit-qt] QtWebkit JavaScript interpreter crash ( v.
> 153112/ppc64le).
> Sent by:        Allan Sandfeld Jensen <carewolf <at> gmail.com>
> 
> On Wednesday 28 October 2015, Atul Sowani wrote:
> > Hi,
> > 
> > I am trying to port PhantomJS 2.0.1 to IBM PPC64LE platform. PhantomJS
> > uses qtwebkit version 153112 and I am facing a few crashes in the
> > JavaScript interpreter code. Is this the right forum to discuss qtwebkit
> > issues I am facing while porting the code?
> 
> Yes.
> 
> I haven't tried PPC64LE myself, when I last touched PPC64 it was to make
> big-
> endian 64bit work, so it might not configure correctly.
> 
> `Allan
Atul Sowani | 28 Oct 12:26 2015
Picon

QtWebkit JavaScript interpreter crash (v. 153112/ppc64le).

Hi,

I am trying to port PhantomJS 2.0.1 to IBM PPC64LE platform. PhantomJS uses qtwebkit version 153112 and I am facing a few crashes in the JavaScript interpreter code. Is this the right forum to discuss qtwebkit issues I am facing while porting the code?

Thanks,
Atul.
_______________________________________________
webkit-qt mailing list
webkit-qt <at> lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt
Konstantin Tokarev | 21 Sep 16:23 2015
Picon

Questions about Qt input method support in WebKit 2

Hi Kenneth,

I'm aware that you are not working on WebKit for a long time, however I'd like to ask you some questions about
your code.

1. In patch [1] what was the motivation for not sending surroundingText in case of
result.isInPasswordField? In this case code from patch [2] sets hints Qt::ImhHiddenText and
Qt::ImhSensitiveData for text coming from password fields. May !result.isInPasswordField check in
[1] be safely removed now?

2. I've found that Element::innerText() used to obtain surroundingText in [1] always returns empty
string at least for HTMLTextFormControlElement descendants (<input> and <textarea>). I've fixed it in
patch [3], however I've left fallback to innerText for other kinds of elements. Are there any other kinds
of editable elements where innerText() was known to work in past?

3. Have you tried to support text removal in WebKit2 via QInputMethodEvent ? I've tried to support event
constructed as

QInputMethodEvent event;
event.setCommitString("",-1,1);

in QtWebPageEventHandler::handleInputMethodEvent() [4] by calling
m_webPageProxy->confirmComposition("", -1, 1), but that didn't work. For now I've surrendered to
sending key events with Qt::Key_Backspace.

[1] https://bugs.webkit.org/show_bug.cgi?id=74080
[2] https://bugs.webkit.org/show_bug.cgi?id=76169
[3] https://codereview.qt-project.org/#/c/125970/
[4] http://trac.webkit.org/changeset/103233/trunk/Source/WebKit2/UIProcess/qt/QtWebPageEventHandler.cpp

--

-- 
Regards,
Konstantin

Gmane