[Webkit-unassigned] [Bug 208129] [GTK] Stop using gtk foreign drawing API to style form controls

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=208129

--- Comment #18 from Adrian Perez <aperez at igalia.com> ---
(In reply to Adrian Perez from comment #17)

> > [...]
> 
> Wild idea: can we expose somehow in the WebKitWebView API the information
> that an embedder might need to render a scrollbar? I think the following
> additions each scrollbar should suffice:
> 
>  - Current position, range [0.0, 1.0].
>  - Size of the viewport vs. page height (to know how long the thumb
>    needs to be).
>  - Whether the web view needs to show a scrollbar (e.g. FALSE if content
>    does not need it, or if CSS has been used to override the default
>    scrollbar look).
>  - A new method to scroll to a given position.
> 
> Am I being too naïve with this idea?

I forgot to mention that this would be only for the topmost scrollbar, the
one attached to the web view itself, and I would not try to handle elements
inside web pages (iframes, textareas, etc.) — rendering for those would still
be done by WebKit.

Related (possibly complimentary) idea: style the controls that WebKit{GTK,WPE}
renders in a way that they do not recall any particular toolkit and are as
neutral as possible, so they blend well in most environments. Currently they
look a tad too much like GTK's Adwaita theme, and while it is not too bad,
the illusion falls apart a little bit when using other themes — specially
when it comes to the scrollbar attached to the sides of a web view, I think
we need a more subtle look there.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20200319/f181f7a2/attachment.htm>