Reviews for New Tab Override
New Tab Override by Sören Hentzschel
32 reviews
- Rated 2 out of 5by Firefox user 14192989, 7 years ago
- Rated 2 out of 5by Firefox user 14156277, 7 years agoI used this extension. At first, it was good and it gave me a blank new tab as I wished. Unless it occupied a huge space in the address bar (that even I could not sometimes find the actual address on the net), I was satisfied. But, after two weeks, I saw my Firefox working terribly, all icons were trembling when I was opening a new tab, it was truly irritating! After I removed this extension I saw Firefox is OK again. I do not know why it happened, just I know there was something wrong.
- Rated 2 out of 5by Firefox user 12472661, 7 years agoThis web extension has too much clutter and makes the process more complicated than needed.
Developer response
posted 7 years agoThat's not true at all. It's not possible to make it easier than entering the URL in an URL field. - Rated 2 out of 5by scsc, 7 years agoDeactivating the extension replaces the current tab content by a default new tab, destroying all data one is working on and even literally erasing the tab from tab history (no way to use Back). Activating the extension instead closes the current tab. Even now, the tab is completely lost in the void, because ctrl+shift+t causes a "new tab" be opened INSTEAD of the previously closed tab. (EDIT: The previously closed tab is only lost due to a hazard when I press ctrl+shift+t twice very fast.)
Other than that, the addon does what it has to do, and I appreciate the option to gain tab focus instead of the navigation bar. One last thing i'd find very useful is if typing into the address bar before anything gets loaded postponed the process of replacing address bar (deleting anything I've typed) and taking the focus away. Not sure if firefox even provides so much API to achieve this.
// Reply: Well the issue is critical and deserves at least an acknowledgement in the description, as it's an anti-feature. Honestly though, I haven't seen WebExtensions implementation, but I don't believe you at all. I can imagine several workarounds, neither of them were even considered. Is there no API whatsoever to access the last closed tab history, so that you can offer a way to manually re-open the lost tab? Is there absolutely no way not to process your addon when the user presses Ctrl+Shift+T? Is that specific event impossible be detected? Can you not let the default implementation (optionally) load first before redirecting to the user specified site? Also the issue could be reported to WebExtensions devs... Completely blocking the "re-open last tab" support is definitely not acceptable as a final decision. (But I know the WebExtensions suck, there are so many other addons that no longer work even in theory in the new Firefox.)
-> Okay so I decided to try to fix my issue myself and even though I found a WebExtensions solution, there was a bug that I couldn't fix. Still, some safety workarounds could be made. Luckily, I found a workaround instead: disabling the focus setting solved the issue, because it still focuses the new page anyway (the setting is broken), thus it works exactly as I wanted. The referenced issue is here: https://github.com/cadeyrn/newtaboverride/issues/167Developer response
posted 7 years agoIt's not the fault of New Tab Override that WebExtenions work this way. - Rated 2 out of 5by ..:: c0d3r ::.., 7 years ago
Developer response
posted 7 years agoAnother two star rating without negative feedback and therefore a spam review… - Rated 2 out of 5by Firefox user 13931907, 7 years agoIt works but often it is slow. I click the new tab icon and then the tab opens and it takes a few seconds to redirect to my homepage. This is annoying when it happens so often. Firefox should have this feature built in!
Developer response
posted 7 years agoI doesn't take "a few seconds" on any of my systems and there were never a similar report in all the years. Please open an issue on Github for support. - Rated 2 out of 5by Firefox user 13479847, 7 years agoOption "local file" doesn't work, "current home page" doesn't work when home page is local file.