You think Fx3’s method is unintuitive? In Chrome you do it by dragging the “add bookmark” star button to the bookmarks bar. Doesn’t bother me, though, as I just click the star since it’s just a single click and I never sort (just search).

Huh, I haven’t used Chrome enough to have realized that. I do know that Chrome’s tab tearing isn’t nearly as sensitive as Firefox’s.

netster007x wrote:

@Ryan: Try dragging the site favicon to to ur bookmarks

Huh, never really thought about that. It just doesn’t seem as intuitive to me though. I wish there was a way to disable the detaching feature, but I’m not sure Mozilla is going to offer that anytime soon. Thanks for the tip though… I’ll be using that.

Sadly after looking high and low, I have found no way of turning off the tab tearing other than reverting back to Beta 1.

@Ryan: Try dragging the site favicon to to ur bookmarks

Huh, never really thought about that. It just doesn’t seem as intuitive to me though. I wish there was a way to disable the detaching feature, but I’m not sure Mozilla is going to offer that anytime soon. Thanks for the tip though… I’ll be using that.

@Ryan: Try dragging the site favicon to to ur bookmarks

That is the way I’ve always been doing it. But I’ve noticed a lot of people try to drag the tab.

One feature they need to fix and/or remove is the tab tearing. It is way too sensitive and a feature I really don’t have a use for. Worse yet I have poured over MozillaZine only to be disappointed to learn there is no way to turn this feature off.

That feature has actually been pissing me off lately. I used to be able to drag tabs into my bookmarks, but with the tab tearing I can’t don’t that anymore. It definitely needs some work.

Back in June when we first started hearing about Firefox 3.1, it was made to sound as if it were going to a simple update from Firefox 3. A chance to get those features that were wanted in Firefox 3, but not quite ready at release time. It wasn’t suppose to be anything major that would cause so many issues with add-ons not working.

I wish that were the case, but they are definitely trying to clean things up in their code as well. It’s their “cleanup” process that killed my extension a few times.

I actually thought they did have that if you’re upgrading through the built-in upgrader. If you’re just downloading the installer, however, I don’t think it checks that. So it’s really just the testers that don’t get this convenience.