I'm wondering whether this is a known issue and whether its being addressed. I'm developing a webapp for a client that will be using Firefox 2.* across the board, and was hoping to use jQuery & Ext to create some very usable components. Unfortunately, this issue might cause me to rethink my approach.
Known issue and already resolved in the upcoming 1.1.3 release. --John
