Closed Bug 644286 Opened 15 years ago Closed 15 years ago

@font-face rendering fails

Categories

(Firefox :: Extension Compatibility, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: theboergers, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0) Gecko/20100101 Firefox/4.0 Build Identifier: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0) Gecko/20100101 Firefox/4.0 Go to http://html5test.com. The score should be rendered in the font PusabRegular but is instead rendered in Arial. Go to http://mytj.org. The header elements should be rendered in the font ChunkFive and is instead rendered in Georgia. In both cases, it failed to render the @font-face font and instead rendered the local fallback fonts. Reproducible: Always Steps to Reproduce: 1. Go to a site with @font-face css rules 2. 3. Actual Results: @font-face rule fails, local fallback font rendered instead. Expected Results: @font-face fonts to render.
Works fine for me using Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.2a1pre) Gecko/20110323 Firefox/4.2a1pre ID:20110323074443. Could you see if the issue occurs if using Firefox in safe mode: http://support.mozilla.com/kb/Safe+Mode How about with a new, empty testing profile? (Don't install any addons into it) http://support.mozilla.com/kb/Basic+Troubleshooting#w_8-make-a-new-profile
Component: General → Layout: Text
Product: Firefox → Core
QA Contact: general → layout.fonts-and-text
Version: unspecified → Trunk
Good call. I isolated the problem to the NoScript extension (2.0.9.9 rc6). I will contact the developer and let him know of the problem. Thanks for taking a look!
You're welcome :-) Note: NoScript deliberately includes font face in the list of things it blocks. You will either need to whitelist the site(s) in question or else: Noscript options -> Embeddings -> Untick "Forbid @font-face"
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Component: Layout: Text → Extension Compatibility
Product: Core → Firefox
QA Contact: layout.fonts-and-text → extension.compatibility
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.