-
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mention other style simplification tools in the README #29
Comments
Just as a footnote, there was a "service" (script) called NotForest (archive, marklets.com entry) which did much of the same thing. Unfortunately the javascript bookmarklet didn't contain the actual javascript code, but instead injected a script tag whose source was http://www.notforest.com/notforest3.js, which I can't find archived anywhere (there are some js files archived here, and a stylesheet which apparently came from the Typominima Wordpress theme, but seemingly was used for the notfrest.com website itself, not for the bookmarklet). That said, here's what one commenter said on hacker news:
It was created by Steve Claridge (rhubarbcustard@HN, steveify@twitter). |
There's also the iReader extension for Firefox and Chrome (archived website, source code), which seems pretty much abandoned. |
Another note: Readability has been retired, and its functionality is now available via the Mercury reader (which only provides an extension for Chrome). |
More relevant stuff:
|
As a useful reference, flattr/flattr-extension#27 lists the reading modes implemented by Firefox, Chrome, Edge and Safari. |
Also related: the notion of classless CSS stylesheets:
Some examples:
|
See also:
Here are some notes comparing the two. |
See also: A look at CSS Resets in 2018, which has a nice overview, including links to the most popular browsers' default stylesheets. |
See also: https://github.com/jensimmons/cssremedy |
Interactive demo pages that allow comparing various minimal/reset styles:
Test pages containing multiple HTML elements:
|
Something like this:
It's worth mentioning that at least one of them had (have?) a bookmarklet, but it didn't work on the client-side -- it replaced the current page with a version parsed in their servers.
The text was updated successfully, but these errors were encountered: