The different images delivered might indicate user-agent based switching which might explain the different behaviour. So there are actually real websites delivering WEBP images. Amazing!

Cheers,
Lars


On Mon, Sep 30, 2013 at 2:32 AM, Rich Coe <rcoe@wi.rr.com> wrote:
On Sun, 29 Sep 2013 21:12:25 +0200
Lars Windolf <lars.lindner@gmail.com> wrote:
> Am 28.09.2013 22:46, schrieb Rich Coe:
> > Any idea how to debug why images from a particular website doesn't
> > display images?  From what I can tell there's nothing wrong with the
> > web page itself.  Firefox doesn't have an issue with it.
> >
> > Both the inline rss feed and the separate tab browse option doesn't display
> > the page.
> That's strange. A good way to debug the RSS feed rendering is to
> start with --debug-html, then to select an item and to check the
> ~/.cache/liferea/output.xhtml in another browser.

Here's some strange results.

- file://.../.cache/liferea/output.xhtml displays normally in firefox

- file://.../.cache/liferea/output.xhtml does not display normally in
    a liferea tab

- I did a wget of the embedded image, call it badimg.gif
  and added a img ref to output.xhtml <img src="file://path/to/badimg.gif">
  and loaded it into the liferea tab -- image displays normally

- I put the image on a remote server and changed the <img src> tag
  to point to it and loaded it into the liferea tab -- image displays normally

When the image comes from the original web server, the Content-type: is
image/webp.

When the image comes from the other web server, the Content-type: is
image/gif.

I found https://bugs.webkit.org/show_bug.cgi?id=105915 which looks like
it's after some version of libwebkit after 1.10.2, like version 2.

I'll try a later version libwebkit.

Rich
--
Rich Coe     rcoe@wi.rr.com