Reviews for FireTitle
FireTitle by Capitaine Fab
4 reviews
- Rated 3 out of 5by Firefox user 14221405, 7 years agoGreat functionality, but slows my firefox down massively. But my FF session might be an edge case with 20 open windows, one of them with 2500 tabs :D
- Rated 3 out of 5by Firefox user 14218530, 7 years agoUnfortunately it does not survive a restart and session restore with multiple windows, which renders it pretty useless. (At least using the MySessions add-on. Not sure about the built in FF session restore. But as that is not reliable, I need an additional add-on. May also be that MySessions is crap, will probably try something else here. That's why it's still 3 stars.). This worked with the old FireTitle and the session manager plugins I was using, the Mozilla has chosen to break :(
Don't show separator if there is no title set. - Rated 3 out of 5by Firefox user 13455483, 7 years agoA good start but FF limitations are affecting it. Howver, letting the Mac variant default to cmd+, (since cmd+; apparently isn't assignable?) is bad and should have been replaced by almost anything else, namely a setting to allow the USER to pick. But the worst shortcoming seems to be that it doesn't save your window titles upon closing Firefox! So when you restart, you have a bunch of windows with the same default names, making it useless. And it can be a pain to go through them all and re-set them properly. Please find a way to store the windows names if FF closes or crashes!
Developer response
posted 7 years agoHi, thank you for your comment. I tried to fix the "names forgotten after closing firefox" bug. However, since I can't reproduce it, I'm not sure it is. Could you try again and tell me? Thanks. - Rated 3 out of 5by Rogério, 7 years agoIt does not work yet, but I'm waiting...
Please, could you at least fix the shortcut to preferences? In mac, COMMAND+, is the system wide Application Preferences. You shouldn't use it for Crappy Firetitle. It broke the Firefox Preferences...Developer response
posted 7 years agoAw, sorry for the bad shortcut (and the long delay). It seems that Command+; is available in new versions of the API. I'll revert back the shortcut to Command+; in version 0.1.8.