Things Have Changed.

If you haven’t noticed, things have changed. There are still issues here obviously but here’s the lowdown. Page is HTML5 or at least roughly. Still some divs in here but such is life. @font-face is getting used all over the place here with the wonderful (though very Gotham-y which might be an issues) Nevis typeface. Fallback is Helvetica just so you know. I have stumbled across an issue which I’ll look into a little later but the just of it is: in Safari Nevis renders in the typeface unaltered as intended. It’s all headings so they default to bold in all browsers but, as I say, Safari just serves up the typeface as intended without styling. Firefox on the other hand fakes the bold on the type which is undesired (unless you’re falling back on Helvetica which is what I want)*. Someone somewhere must have dealt with this previously so there may be an easy fix I don’t know about. I’m kind of the fence about how each browser differs. In one respect, bold is the default and I agree with that, on the other hand, I kind of want @font-face to just serve up the font and browsers don’t touch it. Hmmmm. Anyway, things may change again soon. Who knows! I get bored so easily. Any issues (other than the monthly links on the side, I haven’t hooked those up yet) please let me know.

*Solved. You must specify the same typeface as bold in another declaration if you want Firefox to treat it well. This seems like the right behaviour. CSS3.info to the rescue.

Comments on Signal Response almost never get used for anything other than alerting the general public about pharmaceutical avenues that they may otherwise not know about. If you feel you must comment, go ahead but be cool about it. You can use some markup in here. I'll leave it to you to guess which.