From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: shr - span elements with title attribute, tooltip?
Date: Tue, 29 Mar 2011 13:46:44 -0500 [thread overview]
Message-ID: <87oc4tg3xn.fsf@lifelogs.com> (raw)
In-Reply-To: <m3aagd4whf.fsf@quimbies.gnus.org>
On Tue, 29 Mar 2011 20:23:08 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> It's not difficult. Just render "[title: content]" instead of "content"
>> when the user asks to toggle the title, and give the user a way to do it
>> locally or globally for the whole buffer.
LMI> It doesn't seem very useful to me. The common use case for "title" is
LMI> to add a textual explanation for a non-textual rendering element, which
LMI> is why I've implemented it for <IMG>, and nothing else.
It's commonly used for form and a elements and it's required for abbr
and acronym. Plus it often makes sense for other HTML elements. So I
think it's useful generally, not just for images. But even for
images...
>> Tool tips are (arguably) one of the worst UI elements you can use
>> generally, as they are only intended for controls that don't have space
>> for labels (e.g. toolbars). They require fine control, *a mouse*, and
>> the user to be patient while hovering above something. There is not
>> even a hint that hovering will reveal a tool tip, you just have to hope.
LMI> Yes. Which is why people don't put "title" on random textual objects in
LMI> HTML, but virtually only on images. :-)
...you can't possibly argue that it makes sense for the user to hover
over every image hoping it has a tooltip? That works for XKCD because
the users have been trained by now to play that joke, but not generally.
As I keep saying, tooltips require a mouse while Emacs runs just fine
without a mouse or graphics. So let's just provide a way to toggle
titles in the shr buffer, it's a tiny amount of work. I'll do it if you
don't feel like it--it will be off by default in any case.
Ted
next prev parent reply other threads:[~2011-03-29 18:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-27 7:54 Adam Sjøgren
2011-03-27 8:32 ` [PATCH] Show title attribute of span elements as mouse over text Adam Sjøgren
2011-03-28 18:58 ` shr - span elements with title attribute, tooltip? Ted Zlatanov
2011-03-28 19:17 ` Adam Sjøgren
2011-03-28 19:33 ` Ted Zlatanov
2011-03-28 19:59 ` Adam Sjøgren
2011-03-28 20:14 ` Ted Zlatanov
2011-03-28 20:34 ` Adam Sjøgren
2011-03-28 21:02 ` Adam Sjøgren
2011-03-28 21:07 ` Ted Zlatanov
2011-03-29 17:52 ` Lars Magne Ingebrigtsen
2011-03-29 18:07 ` Ted Zlatanov
2011-03-29 18:23 ` Lars Magne Ingebrigtsen
2011-03-29 18:46 ` Ted Zlatanov [this message]
2011-03-29 19:04 ` Lars Magne Ingebrigtsen
2011-03-29 19:16 ` Ted Zlatanov
2011-03-29 19:35 ` Lars Magne Ingebrigtsen
2011-03-29 19:50 ` Ted Zlatanov
2011-03-29 20:15 ` Lars Magne Ingebrigtsen
2011-03-29 21:31 ` Lars Magne Ingebrigtsen
2011-03-30 6:05 ` Adam Sjøgren
2011-03-30 13:13 ` Ted Zlatanov
2011-03-30 13:39 ` Richard Riley
2011-03-30 19:02 ` Ted Zlatanov
2011-04-03 12:10 ` Lars Magne Ingebrigtsen
2011-03-29 21:15 ` Adam Sjøgren
2011-03-29 21:09 ` Adam Sjøgren
2011-03-30 0:58 ` Kevin Ryde
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=87oc4tg3xn.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).