After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 728002 - (geary-wk2) Port to WebKit2
(geary-wk2)
Port to WebKit2
Status: RESOLVED FIXED
Product: geary
Classification: Other
Component: client
unspecified
Other Linux
: High major
: 0.12.0
Assigned To: Michael Gratton
Geary Maintainers
: 734312 (view as bug list)
Depends on: 720364 764812 765516 776421
Blocks: 686373 712926 712995 713201 713436 713656 713956 714000 714002 714129 714295 714430 714576 726290 730495 743970 750075 766479 770584 772748 773132 777250 778021 778022 778024 778025
 
 
Reported: 2014-04-10 23:32 UTC by Jim Nelson
Modified: 2017-02-28 14:45 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jim Nelson 2014-04-10 23:32:04 UTC
I've been informed by a member of the WebKit team that WebKit 1 has been officially end-of-lifed.  We need to prioritize moving to WebKit 2.

One of the big tasks is that we'll need to build a shared object (essentially a .so) that's loaded by the rendering process and communicates via IPC (D-bus makes sense here) with Geary.
Comment 1 Jim Nelson 2014-08-05 19:48:58 UTC
*** Bug 734312 has been marked as a duplicate of this bug. ***
Comment 2 Hashem Nasarat 2014-09-17 01:51:13 UTC
This will also bring High-DPI support for the message view!
Comment 3 Robert Schroll 2014-10-18 22:48:02 UTC
There is a test case here: https://github.com/rschroll/webkitdom

Note that we needed to fix a WebKit VAPI file to make the DOM event handlers work.  This will presumably make it into Vala 0.26.2.  Until we can require that, I guess we have to build our own VAPI files.
Comment 4 Jim Nelson 2014-10-20 19:44:59 UTC
Another potential way to work around this is to use extern declarations.  Not pretty, but one way to work around VAPI issues if only a couple of methods are problematic.
Comment 5 Christian Stadelmann 2016-02-02 17:21:31 UTC
*Bump*
There are many issues with WebKit 1 Gtk bindings. Please port your code to WebKit 2 Gtk bindings. See https://blogs.gnome.org/mcatanzaro/2016/02/01/on-webkit-security-updates/ for reasons why.
Comment 6 Michael Gratton 2016-04-08 00:00:08 UTC
*** Bug 741866 has been marked as a duplicate of this bug. ***
Comment 7 Michael Gratton 2016-04-09 08:26:20 UTC
WIP up and running here: https://github.com/mjog/geary/tree/wip/widget-conversation-viewer

I'm concentrating on converting to using GTK for displaying individual messages first, where each message in a convo has its own WebKit.WebView. Once that's up to speed, then porting to WebKit2 will be much easier.

More details of the approach in commit messages for that branch. I'm using GitHub while I don't have a GNOME account.
Comment 8 Adam Dingle 2016-04-09 20:40:44 UTC
Sounds good - I'm glad to hear this is underway!
Comment 9 Michael Gratton 2016-10-04 07:10:20 UTC
The fix for Bug 765516 is going to land in the next couple of days, so I'll picking this up this soon.

There are some unfinished issues from that bug that weren't worth fixing until we have ported to WK2, and hence should be fixed as part of this. These include:

 * Known crashers:
   - In libsoup when rapidly changing conversations
   - Displaying some excessively long emails with a wide screen
   - Replying to very long emails

 * Email height related issues:
   - Space bar no longer advances through a conversation by page
   - ListBox jumping around when rows are focused by a click
   - Very long emails being truncated
   - Message web view not resizing when it shrinks in height
   - Implement ConversationListBox::get_selection_view properly

 * Message display:
   - Cannot re-collapse quotes
   - Link warning popover position occasionally incorrect 
   - Message headers are not being printed

 * Composer:
   - Clamp top of embedded composer toolbar to top of list box window & bottom to the bottom

 * Search:
   - Reenable next/prev for find
   - Scroll to first matching message
Comment 10 Michael Gratton 2016-10-14 08:45:27 UTC
Okay, I've started a branch for this and will be pushing it up to GNOME git at wip/728002-webkit2 as it evolves. It's terribly broken at the moment, this is more of a backup and in case anyone is interested, but will be improving over time.
Comment 11 Federico Bruni 2016-10-26 06:56:06 UTC
I confirm the "cannot re-collapse quotes" (a bit annoying).

Another bug (I think): I can no longer mark as special a folded message. The star is visible but greyed out and if I click on it nothing happens; I have to unfold the message and then the click works.
Comment 12 Michael Gratton 2017-02-01 00:09:04 UTC
(In reply to Federico Bruni from comment #11)
> I confirm the "cannot re-collapse quotes" (a bit annoying).

This should be fixed, but it's a bit clunky still - I'll look at refining it a bit.

> Another bug (I think): I can no longer mark as special a folded message. The
> star is visible but greyed out and if I click on it nothing happens; I have
> to unfold the message and then the click works.

Were we discussing this ages ago, on the list maybe? Anyway, this actually by design - the idea being that you probably want to be looking at the message before you decide to star/reply/print/etc it. If it's annoying, and not what 0.11 and earlier let you do, please open a new bug and we can flesh out some use cases and design issues there.
Comment 13 Michael Gratton 2017-02-01 00:09:36 UTC
Fixed on master with commit 29b339c.

I'll open bugs for the outstanding issues I mentioned in comment #9 above that are yet to be addressed.
Comment 14 Michael Catanzaro 2017-02-01 00:38:25 UTC
\o/
Comment 15 Federico Bruni 2017-02-01 12:27:28 UTC
(In reply to Michael Gratton from comment #12)
> (In reply to Federico Bruni from comment #11)
> > I confirm the "cannot re-collapse quotes" (a bit annoying).
> 
> This should be fixed, but it's a bit clunky still - I'll look at refining it
> a bit.
> 

Yes, it's fixed.

> > Another bug (I think): I can no longer mark as special a folded message. The
> > star is visible but greyed out and if I click on it nothing happens; I have
> > to unfold the message and then the click works.
> 
> Were we discussing this ages ago, on the list maybe? Anyway, this actually
> by design - the idea being that you probably want to be looking at the
> message before you decide to star/reply/print/etc it. If it's annoying, and
> not what 0.11 and earlier let you do, please open a new bug and we can flesh
> out some use cases and design issues there.

Actually I'm not 100% sure that 0.11 and earlier let you do so. Anyway, the current idea makes sense, so I won't open a new bug for this. We'll see if other people will be annoyed by this behaviour (I'm not).