[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: fine grained control of webkit browsing

From: Perry E. Metzger
Subject: Re: fine grained control of webkit browsing
Date: Tue, 19 Jun 2018 12:37:16 -0400

On Tue, 19 Jun 2018 18:19:07 +0200 Ricardo Wurmus
<address@hidden> wrote:
> Perry E. Metzger <address@hidden> writes:
> > 2) Say one wants to do things like viewing something with
> > javascript off and without loading remote elements (say because
> > one wants to safely view some HTML email). What does one need to
> > do to get this to work?
> The widget is not fully integrated into Emacs.

It would be neat if it were. One would like, for example,
to be able to move a cursor around in it with keyboard commands,
copy text, and move back to another buffer and paste it without
touching the mouse.

> The extent to which one can conveniently communicate with the widget
> is by sending a string containing a JavaScript program to the widget
> and have it return a value.  Everything else requires exposing
> Webkit API features to Elisp.

Ah, so at the moment, this isn't yet at the point where (for example)
one could safely use it to view HTML email. (To do that, among other
things, one needs to shut off JavaScript and to allow programmatic
control over which images are loaded.)

> Attached is an old patch that I never submitted that allows one to
> set webkit settings via Elisp.  Unfortunately, disabling JavaScript
> for the widget also disables JavaScript evaluation of strings that
> are sent from Emacs -- we use JavaScript for telling the widget to
> scroll, for example. (See ___xwidget-webkit-scroll-bottom___ or
> ___xwidget-webkit-show-element___.)

So it would be necessary to tighten the integration a lot more in
order to make this work as cleanly as one might like?

Perry E. Metzger                address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]