I have noticed the script is a bit slower under FF3. It may be related to the way the event model changed. For instance, before FF3, IIRC, if a piece of code does anything that triggers an event, that event will only fire once the code finishes; now, the event will fire instantly. That already caused an infinite recursion problem that I've fixed. I also implemented a way to mitigate performance problems that arise when the content is frequently altered (think DHTML-heavy sites like Google Maps).

You should use the "Configure Table Floaters..." command and set a nonzero value for "delay after dynamic change". Try that first; if that doesn't help, you can post the URL here or, if you need privacy/confidentiality/whatever, contact me at ddawson at icehouse dot net.

Yes. Please provide me a test case, so I can see the markup that isn't working.

In the meantime, make sure you understand how it's supposed to work:

• The table must start to scroll off the top of the screen before the floaters appear.
• The floaters don't show when the bottom of the floaters is within 10 pixels of bottom of the table, just because there's little point. So if the body is less than 10 pixels tall, you won't see anything for that table.

I should also mention that this is a very FF-specific script. I don't use Opera, so I can't currently make scripts work with it. Maybe I should install it just for that reason.

Anyway, please post a test page somewhere, and I'll take a look.

Just discovered ad adverse side-effect. ("It's not a bug; it's an undocumented feature.") Floaters can appear on printouts, covering content. If in fixed-positioned-floaters mode, they appear at the top of every page; otherwise, they appear wherever the window is scrolled when the printout is sent. So now I need to figure out how to exclude print media. It's easy in a stylesheet, but when styling an element directly, it's another story.