Critiques pour Scroll Progress New
Scroll Progress New par ccdoub
13 notes
- Noté 5 sur 5par García y García, il y a 4 moisan 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. - Noté 5 sur 5par Utilisateur ou utilisatrice 13983020 de Firefox, il y a 5 mois
- Noté 5 sur 5par Utilisateur ou utilisatrice 18054261 de Firefox, il y a 2 ans
- Noté 5 sur 5par Kadircan Ersahin, il y a 3 ans
- Noté 5 sur 5par ManyClouds, il y a 4 ans
- Noté 5 sur 5par Marko, il y a 5 ans
- Noté 5 sur 5par bod, il y a 5 ansFor 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 pageRéponse du développeur
mis en ligne : il y a 5 ansThank 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. - Noté 5 sur 5par Utilisateur ou utilisatrice 14960510 de Firefox, il y a 6 ans
- Noté 5 sur 5par F50, il y a 7 ans
- Noté 5 sur 5par bloomine, il y a 7 ansSimple 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.
Réponse du développeur
mis en ligne : il y a 7 ansGlad you find it useful. Thank you for the rating and review. - Noté 5 sur 5par happysurf, il y a 7 ansIn 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. :-)Réponse du développeur
mis en ligne : il y a 7 ansIt was an issue introduced with the recent code refactoring, thanks for noticed them. Already submited a patch version.