The reading progress bar is a great user experience on longreads. Especially if it accurately depicts the reading progress in the article text, and nothing else. This is standard on single blog posts and enabled by default.
Location top of screen, bottom of screen or below a sticky menu.
Choose color of the reading progress bar.
Have the bar start at 0% even when part of the article is visible.
Select post types you wish the bar to appear, or individual posts.
The reading progress bar has smooth initializing since part of the text may already be visible, after that a lightweight update-function ensures quick response while scrolling.
The bar can attach itself to any (sticky) element that you define as an admin, when there are multiple, the first visible element will be used.
When there is no (longer a) visible element to attach to, the bar displays at the top.
If there is no single article identified (by class names or id) it uses the whole page to calculate progress.
This is my 6th WordPress plugin but my first one freely available to everybody. I hope you enjoy using it as much as I enjoy building it!
Joeri (ruige hond)
Install the plugin by clicking ‘Install now’ below, or the ‘Download’ button, and put the WP-reading-progress folder in your plugins folder
By default it only works on single blog posts and uses an orange colour
Go to settings->WP Reading Progress to customize it
Upon uninstall WP Reading Progress removes its own options and post_meta data (if any) leaving no traces.
Col·laboradors i desenvolupadors
«WP Reading Progress» és programari de codi obert. La següent gent ha col·laborat en aquesta extensió.Col·laboradors
“WP Reading Progress” s'ha traduït a 6 configuracions regionals. Gràcies als traductos per les seves aportacions.
Tradueix “WP Reading Progress” a la teva llengua.
Interessats en el desenvolupament?
Navegueu pel codi, baixeu-vos el repositori SVN, o subscriviu-vos al registre de desenvolupament per fisl de subscripció RSS.
Registre de canvis
1.5.2: simplify progress calculation accounting for incorrect bounding client rect reporting of body
1.5.1: remember (cache) the elements to attach to, for speed
1.5.0: allow multiple menu selectors and pick the first visible one to attach to
1.4.0: compatible with fixed menus that consist of different elements depending on screen size, as long as they have a common selector
1.3.7: added aria-role and aria-value updating for screenreaders
1.3.6: moved css to head to avoid render blocking, added option ‘no css’ if you want to handle it yourself
1.3.5: improved get top position custom function to include edge cases, debounced resize event
1.3.4: removed jQuery dependency
1.3.3: fixed implode deprecated notice
1.3.2: fix getBoundingClientRect does not work on iOS 8 and 9 (at least), now using custom function for it
1.3.1: some optimizations regarding the on scroll function
1.3.0: now positions itself snugly to element using top-margin or fixed automatically to top when element is not in viewport or gone
1.2.5: improved fallback for mobile, added rtl support (html tag must contain dir=”rtl”)
1.2.4: added regular post type to settings, added fallback find post by id when not found by class names, added option to display on specific posts only
1.2.3: fixed bug initializing window height to 0 on page load in some cases
1.2.2: increased compatibility with themes regarding looking for single article
1.2.1: added option to start bar at 0%, slightly optimized progress function
1.2.0: improved behaviour upon resize of the window
1.1.0: now identifies single post reading area for all post-types, fallback to body when not found in DOM
1.0.3: fixed translation, corrected license indication
1.0.2: translated to Dutch