I've found what I think is an issue with TMP 3.5RC1 and Firefox 2.0. With TMP enabled, CTRL-T opens a new tab with a slight delay. The delay is a few hundred milliseconds, and I see my CPU usage spike about 20% very briefly. The problem is that a few hundred millseconds is enough to miss the first character of whatever I'm tryping on the new tab. For example, if I press CTRL-T and then start typing "firefox," I'll usually end up with "irefox" which is really a pain. The problem seems to go away when I disable TMP in FF2.0, and it doesn't exist on the TMP versions for Firefox 1.5.
Would you please take a look at what's happening on a new tab open and advise if there is any way to fix this? I'm thinking it may be a specific option that can be turned off. Happens with TMP default settings as well as with my custom TMP settings.
FF2.0 on Windows XP SP2
AdBlock Plus 0.7.2.1
Context Search 0.3
Download StatusBar 0.9.4.3
Tab Preview 0.3
Tiny Menu 1.2.3
Thanks in advance
Bumping my own post - I think what's happening is that TMP 3.0.5 opens a new tab in the foreground by default and TMP 3.5RC1 actually opens a new tab in the background and then brings it forward.
When I press CTRL-T in 3.0.5, the new tab opens immediately with bold (Untitled) on the tab.
When I press CTRL-T in 3.5RC1, I see the italic text of an unread tab, which switches to the bold (Untitled) text I would expect on a foreground tab. This is what causes the little delay in actually opening a new tab.
Has this changed in TMP? Is it a FF2.0 thing? Any way to fix? Hope the extra information helps.