https://github.com/tophf/autopagerize
Infiniscroll on web pages using a large database of rules. A fully reworked fork of the original extension.
https://github.com/tophf/autopagerize
chrome-extension pager paginate
Last synced: 6 months ago
JSON representation
Infiniscroll on web pages using a large database of rules. A fully reworked fork of the original extension.
- Host: GitHub
- URL: https://github.com/tophf/autopagerize
- Owner: tophf
- License: gpl-3.0
- Created: 2019-04-15T10:32:20.000Z (over 6 years ago)
- Default Branch: master
- Last Pushed: 2024-05-21T22:25:24.000Z (over 1 year ago)
- Last Synced: 2025-03-25T09:11:18.327Z (7 months ago)
- Topics: chrome-extension, pager, paginate
- Language: JavaScript
- Size: 1.12 MB
- Stars: 77
- Watchers: 9
- Forks: 10
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
### A fork of [Autopagerize for Chrome](https://github.com/swdyh/autopagerize_for_chrome)
Fully reworked to reduce memory consumption and increase performance:
* inactivity timeout of the background script is configurable, so you can choose a shorter timeout to conserve memory (~30MB) or a longer timeout to conserve CPU due to a faster checking of URL regexps (from half a second right after start to just a few milliseconds in subsequent checks).
* visited URL's rules are cached in IndexedDB to avoid re-checking thousands of rules
* simple URL regexps are converted to the much faster literal string checks
* the data is stored in IndexedDB
* the content script is added to a web page only if its URL has a matching rule
* the content script unregisters all of its listeners to free up memory, when there are no more pages to load or the extension is toggled off in the popup or via a hotkey
* simple one-time messaging is used to avoid persisting the ports for all tabs
### Differences to the original:
* Generic rules are disabled by default and can be re-enabled per site/pattern (a `*` pattern that matches all sites may be used to restore the old behavior) in the options or the popup. This is because these rules (currently there are three) seem to be useless as the popular sites all have a custom rule, while breaking the page layout on less popular sites a bit too often.
* Exclusions are matched to the full URL now unless there's a `*` at the end. The original extension has been incorrectly treating all non-regexp URLs as prefixes.
* `http://foo.com/bar` - this exact URL
* `http://foo.com/bar*` - URLs that start with `http://foo.com/bar`
* `*.foo.com/bar` - URLs that end in `foo.com/bar`
* `*://*.foo.com/bar*` - URLs that contain `foo.com/bar` anywhere
### New features:
* Configurable hotkeys chrome://extensions/shortcuts:
* On/Off switch
* Show the popup
* Load 1,2,5,10 more pages - four separate commands
* On/Off command in the context menu of the extension icon in the browser toolbar
 
### New features in popup:
* Load 1-100 more pages
* Exclude current page URL/prefix/domain
* Enable generic rules for current page URL/prefix/domain
### New options:
* Custom rules
* Ability to start the database update manually
* Customizable internal parameters
* Import/export
### New DOM event: `GM_AutoPagerizeNextPageDoc`
Fired after downloading the new page so that other scripts may alter it like this:
```js
document.addEventListener('GM_AutoPagerizeNextPageDoc', e => {
const doc = e.relatedTarget;
const url = doc.URL;
for (const el of doc.querySelectorAll('img[alt][title]')) {
el.loading = 'lazy';
}
});
```
### Permissions:
* `wedata.net` - used to update the database of pagination rules from http://wedata.net/databases/AutoPagerize/items_all.json which is stripped of everything except XPath selectors for the page elements and RegExp for the page URL
* `` - required to paginate while you browse according to the database of rules (technically, to find the "next page" and "page body" elements)
* `alarms` - to schedule a database update
* `contextMenus` - to add an "On/off" item to the context menu of the extension icon in the browser toolbar
* `offscreen` - ManifestV3 way of handling DOM/XHR in the background script
* `scripting` - to run the pagination script in the matching tabs
* `storage` - to store the options of the extension
* `tabs` - most notably to restart the paging functionality on extension update, also to notify the tabs that match the URL that you've just manually excluded in the popup
* `webNavigation` - to schedule a pagination check when you navigate to a new URL
### How to limit the site permissions
Chrome allows you to easily limit the extension so it can access only a few sites:
1. right-click the extension icon in the toolbar (or browser menu) and click "Manage" - it'll open `chrome://extensions` details page for this extension
2. click "On specific sites"
3. enter the URL you want to allow
4. to add more sites click "Add a new page"
5. add `http://wedata.net` to keep the database of rules up-to-date.
