Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Why doesn't this render in gnus shr/eww?
Date: Thu, 05 Feb 2015 14:37:30 +1100	[thread overview]
Message-ID: <87fval111h.fsf@building.gnus.org> (raw)
In-Reply-To: <upzczj8zf3pa.fsf@dod.no> (Steinar Bang's message of "Sat, 31 Jan 2015 15:02:41 +0100")

Steinar Bang <sb@dod.no> writes:

>> Have you set `gnus-inhibit-images' or `shr-blocked-images', by any
>> chance?
>
> Er yes... sorry!
>
> But the "Link" should be clickable with <p><a></a> and libxml2 in HTML
> parse mode, shouldn't it?  It isn't clickable for me in this article.

It should be, but the HTML in that article is degenerate:

------------
<img src="http://www.tu.no/incoming/2015/01/02/1200036172.jpg/alternates/h585/1200036172.jpg" alt="Foto: Luminator />
<p>Hindrer at gangfeltene forsvinner om vinteren.</p>

<p><a href="http://www.tu.no/samferdsel/2015/01/03/her-kan-de-fa-gangfelt-som-lyser-oppa-snoen">Link</a>
------------

Note how everything until the href=" in the article is contained within
the alt=" text.

> Also, it only shows the first 8 chars of the alt text (but this may be
> normal...?)  Hm... seems to be the case for all articles.

Yes, it limits the placeholder text (to be replaced by the image), I
think.

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/



  reply	other threads:[~2015-02-05  3:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-30 20:30 Steinar Bang
2015-01-30 23:51 ` Adam Sjøgren
2015-01-31  0:49 ` Lars Ingebrigtsen
2015-01-31 14:02   ` Steinar Bang
2015-02-05  3:37     ` Lars Ingebrigtsen [this message]
2015-02-05 17:19       ` Steinar Bang
2015-02-05 20:24         ` Steinar Bang
2015-02-06 10:03           ` 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=87fval111h.fsf@building.gnus.org \
    --to=larsi@gnus.org \
    --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).