liferea
liferea copied to clipboard
lwindolf
Extended image format support for Reading Mode
Right now it seems that sites that host upcoming image formats like webp/avif/heic/heif load placeholder images that can't be viewed in reader mode, though exiting reader mode allows the internal browser to fully-display the content. Are these formats maybe not in the list of filetypes considered "article content"?
Reader Mode for Phoronix:
Internal Web-Browser for Phoronix:
Liferea View Image:
This was actually a base URL problem. You see this in your 3rd screenshot where the image path is broken.
I cannot reproduce this anymore with master. Please retest!
Sorry for the mis-report. I'll retest if I can get it to compile for my distro (or if this fix is in a new tag)
I'm finding that with v1.13.9 and (I guess the base url changes/fixes), that most every article source that used to render mostly correctly, fail to render at all and instead load the full page in the internal Liferea Browser.
Phoronix, as used above, behaves this way now:
The error message: Reader Mode Not Possible. Loading URL unfiltered...
@Saijin-Naib That's strange. I cannot reproduce this regression (tested with Phoronix and the same article you selected).
There was an Readability.js upgrade included in 1.13.9 though...
Reopening the issue because there are still non-rendering images (due to missing base URI) when used with Phoronix website + reader mode. In this case no base URI is set at all anywhere in the rendering output.
So the relative image issue was fixed for item viewing, but not for viewing websites.
@Saijin-Naib That's strange. I cannot reproduce this regression (tested with Phoronix and the same article you selected).
There was an Readability.js upgrade included in 1.13.9 though...
Would my settings for each source impact this? It seems random as some articles in a troublesome feed will work seemingly at random, same for feeds that normally work having failed article loads as well.
Anything I can provide for you to test/reproduce?
@Saijin-Naib Sorry, about taking so long to work on it. No, there is nothing on your side to workaround. It needs to be fixed in the code.