5점중 1점 받음

작성: Guardian., 날짜: 12월 5, 2012 ·

The difference between other users that have this issue is that I'm on Win7.

Here's some info you may need:

Win7 64b, FF 17.0.1

This extension is vital, if you can find a solution for this issue, we'd greatly appreciate it.

Thanks.

이 검토는 현재 부가 기능의 이전 (1.0.1-signed) 버전에 대한 것입니다. 

작성: Eric Caron (개발자), 날짜: 12월 5, 2012 ·

Can you post a step-by-step walk through, with actual links, to reproduce the issue? Posting it on the GitHub issue for this problem - https://github.com/ecaron/firefox-font-fonder/issues/1 - would be great.

5점중 5점 받음

작성: Guardian., 날짜: 5월 21, 2012 ·

While using it a few seconds ago I came up with this idea/suggestion:

Is there a way you could consider adding the feature of having Font Finder detect if the font being rendered is coming from the @font-face declaration in the CSS (or which CSS if you have several CSS files) or if it's coming from your local font folder?

The thing is that in order to troubleshoot font rendering issues sometimes one needs to test if the @font-face (or web font service for that matter) is actually working, or if the font rendered is being pulled from the local /fonts folder.

Thanks for such great extension.

이 검토는 현재 부가 기능의 이전 (1.0.1-signed) 버전에 대한 것입니다. 

작성: Eric Caron (개발자), 날짜: 5월 21, 2012 ·

Although that's a great idea, currently Firefox's code isolates us from knowing the true source of the font and makes a font-face declaration indistinguishable between any web-font or locally loaded font.

As soon as that capability becomes available within Firefox, we'll quickly add it to FontFinder.