I just added the readability package to the [AUR](https://aur.archlinux.org/packages/nodejs-readability-git/).
Not much of a difference from using npm directly, but, personally, (i) I prefer to manage all my (important) packages using yay, and (ii) like to perform all system upgrades from one place (i.e. yay --devel).
Until per-domains stylesheets are implemented, there is no way to
apply style to the readability page only. With this patch, you can
just use the global setting `content.user_stylesheets` by writing
a more specific CSS selector. For example:
body.qute-readability {
font-family: Libertinus;
font-size: 1.2em;
text-align: justify;
}
will change the font and text alignment of the readability page,
without altering the style of other websites.
Before, the first line of a `code` element within a `pre` element had indentation/padding applied to it, creating the illusion that the line started with a space. Now, all the lines in `code` elements horizontally align.
Before, the first line of a `code` element within a `pre` element had indentation/padding applied to it, creating the illusion that the line started with a space. Now, all the lines in `code` elements horizontally align.
Previously, this userscript always assumed the user wanted to parse
the current page. However, this meant that something like `:hint all
userscript readability-js` wouldn't work. To fix this, the script now
checks if qutebrowser is in hinting mode, and sets the page to be
processed accordingly.
An alternative solution would be to rewrite this script to rely on
`QUTE_URL`+`JSDOM.fromURL` accross the board. However, using `QUTE_HTML`
when the target page is already loaded seems faster, uses less data, and works offline.
Rijnder Wever
Florian Bruhin
rnhmjoj