From: Ricardo Wurmus <rekado@elephly.net>
To: Arne Babenhauserheide <arne_bab@web.de>
Cc: 34128@debbugs.gnu.org
Subject: [bug#34128] [PATCH] add emacs built with xwidgets-support
Date: Wed, 23 Jan 2019 09:19:49 +0100 [thread overview]
Message-ID: <87munr7ply.fsf@elephly.net> (raw)
In-Reply-To: <877eew70ge.fsf@web.de>
Arne Babenhauserheide <arne_bab@web.de> writes:
> Hi Ludovic,
>
>> Thanks for the patch!
>
> Thank you for your review!
>
>> I wonder why this hadn’t been done before;
>> Nicolas, Alex, Pierre, thoughts?
>
> There is an older bug with xwidgets support which had problems because
> it depended on an old version of webkitgtk (I only found it after I sent
> the patch). Maybe that stopped others from submitting.
I performed the migration of the Emacs xwidgets feature from the old to
the newer webkitgtk API, but that’s when I noticed that xwidgets are
hardly usable in its current state. I certainly wouldn’t use it as a
browser, for example, because there is virtually no integration with the
rest of Emacs.
It works fine for sending JavaScript snippets to the widgets and have it
respond, but it’s not very well integrated into Emacs. Disabling
JavaScript has the effect of disabling *all* JavaScript, which makes
scrolling impossible (as it is implemented by sending JavaScript to the
widget).
Turning it into a usable browser would require more fundamental changes,
and that’s when I stopped working on patches.
--
Ricardo
next prev parent reply other threads:[~2019-01-23 8:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 22:29 [bug#34128] [PATCH] add emacs built with xwidgets-support Arne Babenhauserheide
2019-01-22 21:48 ` Ludovic Courtès
2019-01-22 23:10 ` Arne Babenhauserheide
2019-01-23 8:19 ` Ricardo Wurmus [this message]
2019-01-23 9:37 ` Arne Babenhauserheide
2019-01-23 9:53 ` Ludovic Courtès
2019-01-23 11:41 ` Ricardo Wurmus
2019-01-23 22:29 ` bug#34128: " Ludovic Courtès
2019-01-24 19:06 ` [bug#34128] " Arne Babenhauserheide
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87munr7ply.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=34128@debbugs.gnu.org \
--cc=arne_bab@web.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).