Recenzije za Scroll Progress New
Scroll Progress New od ccdoub
13 recenzija
- Ocijenjeno s 5 od 5od García y García, prije 12 danaan 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. - Ocijenjeno s 5 od 5od Korisnik Firefoxa 13983020, prije 2 mjeseca
- Ocijenjeno s 5 od 5od Korisnik Firefoxa 18054261, prije 2 godine
- Ocijenjeno s 5 od 5od Kadircan Ersahin, prije 3 godine
- Ocijenjeno s 5 od 5od ManyClouds, prije 4 godine
- Ocijenjeno s 5 od 5od Marko, prije 5 godina
- Ocijenjeno s 5 od 5od bod, prije 5 godinaFor 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 pageOdgovor programera
objavljeno prije 5 godinaThank 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. - Ocijenjeno s 5 od 5od Korisnik Firefoxa 14960510, prije 6 godina
- Ocijenjeno s 5 od 5od F50, prije 7 godina
- Ocijenjeno s 5 od 5od bloomine, prije 7 godinaSimple 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.
Odgovor programera
objavljeno prije 7 godinaGlad you find it useful. Thank you for the rating and review. - Ocijenjeno s 5 od 5od happysurf, prije 7 godinaIn 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. :-)Odgovor programera
objavljeno prije 7 godinaIt was an issue introduced with the recent code refactoring, thanks for noticed them. Already submited a patch version.