Before this is pushed, as I can't test right now: does the search start immediately? If it does, please check how Okular delays it slightly to allow users to type more characters without starting an "heavy" operation.

In D19555#425592, @ltoscano wrote:

Before this is pushed, as I can't test right now: does the search start immediately? If it does, please check how Okular delays it slightly to allow users to type more characters without starting an "heavy" operation.

The search only start after clicking enter and when searching the search field is disabled, as it was previously. Should I change this behavior and add a small delay?

In D19555#425596, @ltoscano wrote:

Oh, right. Thanks.

As a next patch in khelpcenter, I wanted to replace the khtml view with qtwebengine. By doing so, I think we could use an update css style sheet in the view (like this: http://docs.carlschwan.eu/stable5/en/extragear-base/kcontrol/wacomtablet/stylus.html#pen-button-settings) .

Before I start, do you think this is a good idea? Any tips? 😄

In D19555#425601, @ognarb wrote:

In D19555#425596, @ltoscano wrote:

Oh, right. Thanks.

As a next patch in khelpcenter, I wanted to replace the khtml view with qtwebengine. By doing so, I think we could use an update css style sheet in the view (like this: http://docs.carlschwan.eu/stable5/en/extragear-base/kcontrol/wacomtablet/stylus.html#pen-button-settings) .

Before I start, do you think this is a good idea? Any tips? 😄

I'd prefer to keep a choice of the rendering part, so not qtwebengine-specific.

The problem right now is that the KHTMLPart also embeds a lot of other details that should be moved somewhere else, so that other rendering kparts can be plugged-in (the old kwebkitpart, or a new, still unwritten, basic QtTextDocument-based kpart.

I understand the need for updating the style, but maybe we could have a simpler theme that looks similar but it does not need the latest version of CSS.
Anyway, as long as there is no an hard-dependency on qtwebengine, I'm fine.

In D19555#425603, @ltoscano wrote:

In D19555#425601, @ognarb wrote:

In D19555#425596, @ltoscano wrote:

Oh, right. Thanks.

As a next patch in khelpcenter, I wanted to replace the khtml view with qtwebengine. By doing so, I think we could use an update css style sheet in the view (like this: http://docs.carlschwan.eu/stable5/en/extragear-base/kcontrol/wacomtablet/stylus.html#pen-button-settings) .

Before I start, do you think this is a good idea? Any tips? 😄

I'd prefer to keep a choice of the rendering part, so not qtwebengine-specific.

The problem right now is that the KHTMLPart also embeds a lot of other details that should be moved somewhere else, so that other rendering kparts can be plugged-in (the old kwebkitpart, or a new, still unwritten, basic QtTextDocument-based kpart.

I understand the need for updating the style, but maybe we could have a simpler theme that looks similar but it does not need the latest version of CSS.
Anyway, as long as there is no an hard-dependency on qtwebengine, I'm fine.

Ok I will try to implement a simpler css theme that work with ktml. ;)