From: Jim Porter <jporterbugs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: cpardo@imayhem.com, emacs-devel@gnu.org
Subject: Re: Drawing UI elements behind text
Date: Sun, 10 Nov 2024 11:29:27 -0800 [thread overview]
Message-ID: <cb351984-b440-0118-0ed7-36d49f4600f2@gmail.com> (raw)
In-Reply-To: <867c9alwqv.fsf@gnu.org>
On 11/10/2024 11:22 AM, Eli Zaretskii wrote:
> Once the display engine knows at what X coordinate the image slice
> should start, it can stop laying out other display elements and switch
> to the slice when that X coordinate is reached.
I was thinking more about the Y coordinates and having gaps between
consecutive slices if we made a mistake. That's probably fixable, but it
seems like it would require a lot of care to avoid bugs.
>> Or what about applying text scaling?
>
> How is this different from what we do today when text-scaling happens
> in a buffer where images are displayed together with text?
I'm just worried about this due to seeing some similar bugs come up in
the visual-wrap-prefix-mode code.
>> I suppose if we deemed this feature important, we could probably address
>> all of those, but I'm not sure it's worth the effort.
>
> What alternative do we have? Showing the images alongside text
> without letting the images scroll with the text (vertically and
> horizontally) will not fly. How do you scroll the images with the
> text except by displaying them as part of the "normal" display layout?
Personally, I'm ok with saying we just don't support laying out images
like this in EWW. For it to have a practical effect, we'd probably need
to have more-complete CSS support anyway. That's not easy either (though
I have some ideas about how we could do it if we thought it would be
worthwhile).
next prev parent reply other threads:[~2024-11-10 19:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-10 16:39 Drawing UI elements behind text Cecilio Pardo
2024-11-10 18:09 ` Jim Porter
2024-11-10 18:44 ` Eli Zaretskii
2024-11-10 19:06 ` Jim Porter
2024-11-10 19:22 ` Eli Zaretskii
2024-11-10 19:29 ` Jim Porter [this message]
2024-11-10 19:42 ` Eli Zaretskii
2024-11-24 23:37 ` JD Smith
2024-11-26 23:19 ` Cecilio Pardo
2024-11-27 14:36 ` Eli Zaretskii
2024-11-27 18:28 ` Cecilio Pardo
2024-11-27 18:58 ` Eli Zaretskii
2024-11-27 20:01 ` Cecilio Pardo
2024-11-27 20:12 ` Eli Zaretskii
2024-11-27 20:30 ` Cecilio Pardo
2024-11-28 6:53 ` Eli Zaretskii
2024-11-28 8:43 ` Cecilio Pardo
2024-11-28 9:57 ` Eli Zaretskii
2024-11-28 10:41 ` Cecilio Pardo
2024-11-28 11:56 ` Eli Zaretskii
2024-11-28 12:09 ` Cecilio Pardo
2024-11-27 21:15 ` JD Smith
2024-11-27 21:47 ` Cecilio Pardo
-- strict thread matches above, loose matches on Subject: below --
2024-11-27 2:31 JD Smith
2024-11-27 18:33 ` Cecilio Pardo
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=cb351984-b440-0118-0ed7-36d49f4600f2@gmail.com \
--to=jporterbugs@gmail.com \
--cc=cpardo@imayhem.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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.