Iceggiren i Scroll Progress New
Scroll Progress New sɣur ccdoub
13 n yiceggiren
- Yettwasezmel 5 ɣef 5sɣur García y García, hace 10 mesesan excellent extension that's absolutely essential in my opinion. It's unobtrusive and provides an exact
percentage of how much of a page you've read before vanishing.
It's particularly useful if you value *screen real estate* and prefer non-distracting elements in your daily workflow. - Yettwasezmel 5 ɣef 5sɣur Aseqdac Firefox 13983020, hace un año
- Yettwasezmel 5 ɣef 5sɣur Aseqdac Firefox 18054261, hace 3 años
- Yettwasezmel 5 ɣef 5sɣur Kadircan Ersahin, hace 3 años
- Yettwasezmel 5 ɣef 5sɣur ManyClouds, hace 5 años
- Yettwasezmel 5 ɣef 5sɣur Marko, hace 6 años
- Yettwasezmel 5 ɣef 5sɣur bod, hace 6 añosFor years I have used many extensions, never wrote a review before.
This is a Really useful addition. For some time I have been wanting to quickly find my scroll place on large articles. This helpful extension gives me easy control over the web pageTiririt n ineflayen
yeffeɣ-d deg hace 6 añosThank you for the review. I also use this extension https://addons.mozilla.org/es/firefox/addon/scrolly-marks/ for this purpose. It has few users, but is very useful and is very well written. - Yettwasezmel 5 ɣef 5sɣur Aseqdac Firefox 14960510, hace 7 años
- Yettwasezmel 5 ɣef 5sɣur F50, hace 7 años
- Yettwasezmel 5 ɣef 5sɣur bloomine, hace 8 añosSimple and effective add-on useful for people like me who completely hide the huge scrollbars in Firefox Quantum. In addition, in long pages of text it helps to remember the position of the most important passages. Thank you.
Tiririt n ineflayen
yeffeɣ-d deg hace 8 añosGlad you find it useful. Thank you for the rating and review. - Yettwasezmel 5 ɣef 5sɣur happysurf, hace 8 añosIn some web sites the percent number is not on top but remain behind on some page element.
This happen on Netvibes and Reddit, on Techdows.com the font change.
Thanks.
EDIT: The version 1.3.2 works perfectly on Firefox 63beta. :-)Tiririt n ineflayen
yeffeɣ-d deg hace 8 añosIt was an issue introduced with the recent code refactoring, thanks for noticed them. Already submited a patch version.