Not rendering here . . . wait . . . need to check this FF version as it’s different than the home computer . . . PROBLEM - this is FF 3.5. Let me upgrade and try it again . . .
@kohoutek - sorry to go off at a tangent here, but when I visit that link in FF, I have to enable JavaScript before the Tangerine font kicks in. I thought @font-face is pure CSS? Why does it require JS?
I found the culprits. The first culprit is what Paul has already mentioned; The extra comma needs to go, like Paul said in post #26. The second issue is the path in your CSS. You need to add “css/” to your paths.
I know, but it didn’t work on his site. It doesn’t make sense to me, but that’s the only way the font displayed in Firebug when I tested it two or so hours ago. It only worked when I added the css dir to the path. Anyway, I added the code I posted above to Rick’s live site via Firebug (I set it on the .ttf font) and it worked in Firefox, the fonts displayed. I’m out of ideas if Paul’s solution and the fixing of paths don’t resolve the issue.
The fonts are working for me in Firefox now. Perhaps it was removing the comma that did it. Strangely, though, the font urls still return a 404. Bizarre.
Insomnia strikes again. Obviously, when you use the web developer tools in FF, fonts won’t show while testing, just like bg images and the like with relative paths which is why it worked when I added css to the path. It’s just the comma as Paul indicated that was causing the ruckus.