From: Eli Zaretskii <eliz@gnu.org>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: larsi@gnus.org, 28907@debbugs.gnu.org
Subject: bug#28907: 26.0.90; [eww] some problems in input/textarea
Date: Fri, 15 Dec 2017 11:03:59 +0200 [thread overview]
Message-ID: <83h8sstla8.fsf@gnu.org> (raw)
In-Reply-To: <b4mr2rzdopi.fsf@jpl.org> (message from Katsumi Yamaoka on Wed, 13 Dec 2017 17:19:53 +0900)
> Date: Wed, 13 Dec 2017 17:19:53 +0900
> From: Katsumi Yamaoka <yamaoka@jpl.org>
> Cc: Lars Ingebrigtsen <larsi@gnus.org>
>
> On Fri, 17 Nov 2017 17:42:35 +0900, Katsumi Yamaoka wrote:
> > Some generic editing commands, except for `undo', now almost work
> > in input/textarea. To try writing something in those fields, you
> > can use the following two pages:
>
> > <https://html.com/tags/input/#Code_Example>
> > <https://html.com/tags/textarea/#Code_Example>
>
> I've completed the `undo' feature used in eww's editable fields.
> It supports undo/redo-switching and works just like Emacs's undo.
> The last (hopefully) patch containing changelog entries is here:
>
> <http://www.jpl.org/tmp/eww.el-20171213.patch>
>
> I would like to apply it to the emacs trunk if it is acceptable.
Looks good to me, thanks.
Does this implement new user-level features, or just fix bugs? In the
former case, a NEWS entry describing user-visible changes would be
appropriate.
next prev parent reply other threads:[~2017-12-15 9:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 8:39 bug#28907: 26.0.90; [eww] some problems in input/textarea Katsumi Yamaoka
2017-10-27 13:31 ` Eli Zaretskii
2017-10-29 23:30 ` Katsumi Yamaoka
2017-11-02 7:39 ` Katsumi Yamaoka
2017-11-10 7:57 ` Katsumi Yamaoka
2017-11-10 8:28 ` Eli Zaretskii
2017-11-10 9:10 ` Katsumi Yamaoka
2017-11-14 8:26 ` Katsumi Yamaoka
2017-11-17 8:42 ` Katsumi Yamaoka
2017-12-13 8:19 ` Katsumi Yamaoka
2017-12-15 9:03 ` Eli Zaretskii [this message]
2017-12-15 9:58 ` Katsumi Yamaoka
2017-12-27 21:12 ` Lars Ingebrigtsen
2018-04-12 22:30 ` Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83h8sstla8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28907@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=yamaoka@jpl.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.