all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Csepp <raingloom@riseup.net>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	67029@debbugs.gnu.org, Csepp <raingloom@riseup.net>
Subject: bug#67029: 29.1; EWW mode text entry literally unusable on Brutaldon
Date: Fri, 29 Dec 2023 00:27:37 +0100	[thread overview]
Message-ID: <87v88hnbui.fsf@riseup.net> (raw)
In-Reply-To: <CADwFkmnPyF9+NAgWnnpUoaWAUgrBsSKbUnZiPqZxrKPRR-yHeQ@mail.gmail.com>


Stefan Kangas <stefankangas@gmail.com> writes:

> tags 67029 + moreinfo
> thanks
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> From: Csepp <raingloom@riseup.net>
>>> Date: Thu, 09 Nov 2023 23:07:35 +0100
>>>
>>> Since this is mostly a layout bug, I will link to this post with the
>>> relevant screenshots:
>>> https://merveilles.town/@csepp/111382791844555493
>>>
>>> Should be easy to replicate with a multi-line text entry field with a
>>> set number of rows and of a certain line width.  Just try to enter any
>>> text longer than the line character limit.
>>
>> Thanks, but I'd appreciate a recipe to reproduce the problem, starting
>> from "emacs -Q".  The above page renders weirdly with the browsers I
>> have here, and from what I see I couldn't figure out how to reproduce
>> what you show.  A recipe will be great.
>
> Ping.  It seems like we need more information to make any progress here.

Haven't gotten around to it yet, sorry.  The specific case is only
slightly tricky, but the general case (can't enter text longer than box)
seems to be a universal issue across every system I've tried.
A hopefully simple fix would be to just do what w3m does and open a
separate buffer.





  reply	other threads:[~2023-12-28 23:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-09 22:07 bug#67029: 29.1; EWW mode text entry literally unusable on Brutaldon Csepp
2023-11-10  6:54 ` Eli Zaretskii
2023-12-24 14:46   ` Stefan Kangas
2023-12-28 23:27     ` Csepp [this message]
2023-12-29  1:46       ` Stefan Kangas
2024-02-24 16:04         ` Csepp

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=87v88hnbui.fsf@riseup.net \
    --to=raingloom@riseup.net \
    --cc=67029@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=stefankangas@gmail.com \
    /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.