Rated 1 out of 5 stars

It does not work with SeaMonkey 2.49.3.

Rated 3 out of 5 stars

I absolutely love this extension, its one of the most valuable in my toolbox, unfortunately it's not compatible with the latest version of firefox, so I'm hoping the developers are able to rectify that very soon, but definitely a brilliant extension.

Rated 4 out of 5 stars

bibbolo may have some other add-on causing a conflict. I use a number of add-ons (no other font ones), and Font Finder 1.2.3 (which was current at the time of the bibbolo review) works great. It also does things that the WebExtension version, Font Finder (revived) 0.1.8 does not. In particular, it has the extra context menu options "Adjust element's [...]", "Replace font (entire DOM)", and "Disable font (entire DOM)".

The WebExtension version claims it, too, has the "Any active element can have any piece of the font's options (such as color, size or family) adjusted inline" functionality, but this does not appear to be true. The only context menu item is "Inspect Font", and none of the fields in its popup are modifiable. I also checked the screenshots and the FAQ (which, BTW, uses the misspelling "Fond Finder" in multiple places), to no avail.

I'm giving this XUL version of the extension 4 stars rather than 5 due to two issues. One is that it didn't actually address the problem I installed it for. The description says "Information Captured: [...] Font family (including actual font being rendered!)", which I was expecting to help me debug the problem I was having on Linux with extremely messed-up scaled-bitmap, all-caps font substitutions (even when the exact TrueType font specified in the stylesheet was installed). Unfortunately it doesn't tell you the "actual font being rendered" — it just tells you the font that the web page *requests* to be rendered. I then learned about running Firefox with the environment variable FC_DEBUG=1, but its output didn't give me any useful information about the incorrect substitution. Luckily after a bunch more Googling, I was able to figure out that going to about:config and setting gfx.font_rendering.fontconfig.fontlist.enabled = false would cause Linux Firefox to go back to the old Cairo-based font rendering rather than the broken Firefox 44+ version.

The other issue with the add-on is that when you restart for the first time with it installed in a given profile, you get into an infinite loop of popups and new windows or tabs yelling at you to install the WebExtension version instead (despite it not replicating all the functionality of the XUL version). Until you get ahead of it and start hitting OK on the popups, it'll keep on spawning more copies of the popup and more new windows/tabs with the WebExtension version's addons.mozilla.org page loaded. The popups are also modal and won't allow interaction with the window they're related to until you hit OK on that window's popup (even trying to close the window is disabled). Finally, that popup actually gives the opposite advice that it means to: it says "Font Finder is moving to WebExtensions! Please give the WebExtension version a try and replace it with this XUL version." Well, yes, that's just what I've done — I tried the WebExtension version and have replaced it with this XUL version.

Rated 1 out of 5 stars

Simply it doesn't work. It doesn't appear in the context menu and no way to launch it otherwise.

Rated 5 out of 5 stars

不错

Rated 5 out of 5 stars

Useful for Photoshop

Rated 5 out of 5 stars

Great addon for those who work a lot with photoshop!

Rated 5 out of 5 stars

This is a useful extension!

Rated 4 out of 5 stars

Great extension,really worth for use recommended!!

This review is for a previous version of the add-on (1.2.1). 

Rated 1 out of 5 stars

Not work!

This review is for a previous version of the add-on (1.2.1). 

Rated 5 out of 5 stars

This is a good extension. Ease to use. Recommended

This review is for a previous version of the add-on (1.2.1). 

Rated 5 out of 5 stars

I installed some Helvetica fonts and they took over my firefox; this add on fixed and i'm so happy! <3

This review is for a previous version of the add-on (1.2.0). 

Rated 5 out of 5 stars

A colossal thank you to the developers, satify my curiousity everytime whenever I come across beuatiful typography.

This review is for a previous version of the add-on (1.2.0). 

Rated 1 out of 5 stars

Not work with e10s

This review is for a previous version of the add-on (1.2.0). 

Rated 5 out of 5 stars

Very useful for webdesigners or if you're simply curious. Does what it says in the description. A bit slow sometimes but that could also be due to my old machine.

This review is for a previous version of the add-on (1.1.1.1-signed). 

Rated 3 out of 5 stars

The extension is very useful for people who are curious about what font a page is using. However, my problem is that it slows Firefox down dramatically on my computer (Fedora 22, Firefox 39, 2.2 GHz dual-core with 2 GB RAM). I know, not a high-end machine, but without this extension, everything is pretty snappy. With this extension enabled, almost every page has the "Unresponsive Script" dialog asking if I want to stop the scripts on the page. I use several other extensions and none of the others have this problem.

This review is for a previous version of the add-on (1.1.1.1-signed). 

Rated 4 out of 5 stars

Salut!

1) There is no constant effect: font is replaced until page be reloaded.

2) There is no global effect. You replace font on one page of the site, and the other page of the same site has fonts you just tried to eliminate.

3) There is no universal effect at all. Once you try to wipe out Comic Sans from your life, you must replace it on each and every site you meet, each and every time you visit any page.

Conclusion: useful for designers to check layout or to analyse competitors. Not usable for convenient Firefox users.

This review is for a previous version of the add-on (1.1.1.1-signed). 

Sorry for the confusion, End User, but Font Finder isn't meant to be a permanent on-page replacement tool. Its meant for debugging and tuning (much like the Developer Console & Firebug.)

If you're looking for a more permanent solution, maybe something powered by GreaseMonkey could serve your needs.

Rated 3 out of 5 stars

My initial testing was too optimistic. There are some issues.

It's toolbar icon in the customization menu is broken(but not after being placed on the bars.) However, I wont risk keeping it there because buggy icons destroy custom setups.

It also is failing when tested on this very page. It is able to get the font in some sections- and in others it wrongly claims multiple element selections.

I like the extension- but it needs some work.

This review is for a previous version of the add-on (1.1.1.1-signed). 

Rated 1 out of 5 stars

This extension is worse than useless because, although it shows the correct font stack, it can actually show the wrong rendered font.

For example, I have a stack that starts with Georgia, Times, etc... This extension claims that the font actually rendered is Times, but that's simply untrue; Georgia is available and is being rendered. Although they're fairly similar fonts, I know the difference between the two -- just zoom in on a lower-case "i" or "j" and it's obvious. (I used to teach typographic design.) Anyway, just to make sure I wasn't making a mistake, I checked it against a font book. I wasn't wrong; the extension was.

I don't know what the problem is with this extension. Might it be because I'm using an older version of Mac OSX? (Snow Leopard, 10.6.8.) Hard to believe that would matter... and if there's a compatibility issue, it should just refuse to work at all. Anyway, until they correct this bug, I advise people to avoid it because it could confuse you big-time.

By the way, they do seem to have fixed the entirely different problem I reported back in 2012, in my prior 1-star review. I thought I'd give this another chance now. Oh well.

This review is for a previous version of the add-on (1.1.1.1-signed).  This user has a previous review of this add-on.

Can you put up an example on http://jsfiddle.net/? That would be incredibly useful in helping us fix it. We detect the font based on replaying the CSS' stack and then stubbing a bunch of elements to find a matching height/width (that's why fixed-width fonts won't work.)

I've been playing with a new mechanism against more modern versions of FF, but a live example of an unhappy result would really help me vet the possible new solution.

Rated 5 out of 5 stars

All info packed in one. Exactly what I need

This review is for a previous version of the add-on (1.1.1.1-signed).