Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: shr - span elements with title attribute, tooltip?
Date: Mon, 28 Mar 2011 14:33:04 -0500	[thread overview]
Message-ID: <87tyenjb0v.fsf@lifelogs.com> (raw)
In-Reply-To: <8762r3jbq2.fsf@topper.koldfront.dk>

On Mon, 28 Mar 2011 21:17:57 +0200 asjo@koldfront.dk (Adam Sjøgren) wrote: 

AS> On Mon, 28 Mar 2011 13:58:52 -0500, Ted wrote:
>> What if two such titled span elements are nested?

AS> When in HTML-land, do as the browser do, I'd say. I.e. last/closest one
AS> wins:

AS>  * http://koldfront.dk/misc/gnus/span.html

AS> (If you save the example, you can use M-x shr-visit-file to check if it
AS> works as in the browser of your choice.)

The problem is that shr.el is not as capable as a web browser so it's
hard to tell what spans are nested and how.  So you don't necessarily
know what you're pointing to.  This is actually a problem in regular web
browsers too--I use the Chrome and Firebug "inspect element" all the
time.

>> Maybe it can be an `shr-show-titles' toggling command on an article,
>> like `t' toggles the headers? I think we already have something like
>> that for toggling images in the shr renderer, right?

AS> How would you render the titles?

Instead of span1 span2 I'd render [title1: span1] [title2: span2] but
the actual visual is not too important.  It could be customizable as a
`format' HTML string for instance.

Ted




  reply	other threads:[~2011-03-28 19:33 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 [this message]
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
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=87tyenjb0v.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).