Hm. They're working fine for me (Firefox and Safari tested just now). They're disabled by default until there's content in your message body, but there's a couple of conditions where they can accidentally become disabled and not become reenabled. Firefox also has an annoying feature/bug that causes them to stay disabled on a page reload, which is possibly outside our control.

The Javascript also changed a little bit yesterday. It might be worth forcing Firefox to get the latest version of www.serato.com, just incase that's the problem.

I am on FF 3.0.1 and they don't get enabled even after typing in text.




Reloaded that page a few times (is that how you get the latest version?) and the problem still persists.

Hmm. I just tried again on FF 3.0.1 as a non moderator user (the JS works a bit different for mods), and it worked fine...

It may be that you still don't have the latest JS file. I had a problem yesterday with Firefox refusing to get the latest version of the file until I restarted it. I suspect their caching code has had a bug introduced recently.

Are you seeing any JS errors in Firefox's error console (or Firebug, if you have it)?

Hm, I haven't changed anything in my browser... and suddenly it works. Weird.

However I get these following errors/warnings in the console:

I bet it was Firefox too aggressively caching the JS file. They need to fix that.

The first of those warnings, I have no idea - never seen it. But the second one is fine. It just means we're using a CSS property that Firefox doesn't support yet.

How do I force a reload of that JS file?

I had to restart Firefox yesterday when it was refusing to get the latest version of the file. On previous versions of Firefox just doing a page refresh would do it, but it seems not the latest version.

ctrl+F5 should force a reload of all files associated with the page css, script, images etc.

Good to know, thanks nobspangle!

It should. But it isn't in the latest build. At least not for me.