51 reviews
  • Simple and effective
  • I was going to say that: This addon was not necessary anymore because Mozilla has changed the Firefox configuration BUT I was wrong. Although dom.targetBlankNoOpener.enabled has been changed from "true" to "false" in the config file yet no one is protected. Everyone should test it here: https://mathiasbynens.github.io/rel-noopener/
    Edit (after developer response):
    Strange, because for me it did not fail. The test worked once your addon was activated. I suppose it's linked with another tweak I have done in the FF about:config page...
    Thank you for your review! I'm also keeping a close eye on the changes they are planning/making lately.

    (Please note that with this add-on installed, the test you linked still "fails". This is because DTMT allows 'noopener' when target links are from the same domain.)
  • This is a perfect example of why extensions need to exist. Browser vendors can't decide to fix this security hole (in hopes of not breaking old websites), and this extension takes matter into its own hands to protect users from the common pitfall of developers forgetting (or not knowing) to include the rel="noopener". I was slightly concerned at the permission to "Access your data for all websites", however after downloading I opened up the source code and found for myself that the developer was genuine in his description. Thanks for some great simple software!
  • much better than useless "dom.targetBlankNoOpener.enable" that break the internet.
    Hi! Thanks for your review!

    While I'm happy to see that steps are being taken to make the behavior of this add-on a standard, in my experience, adding 'rel=noopener' to ANY 'target=_blank' hyperlink breaks quite a few websites. (Even this add-on's milder implementation breaks a few websites that have unnecessary navigational logic in place.)

    Rest assured, this add-on will be available in any form necessary to give us control over 'rel=noopener' while websites and browsers are figuring out how to live in peace without breaking user experiences.
  • just installed this extension after reading description and reviews. rating 4 stars off-the-bat for your user-friendly description, transparency and pro-active and polite review responses--and as thanks for your effort creating it.

    also reviewing early so i don't forget. anything going awry is usually prompt-enough for a commensurate review, but when everything goes well, i usually forget to review at all.
  • This is a really useful extension. Made my browsing experience a heck of a lot better.

    The only thing missing is the option to apply the rel=noopener to links to the same site (to fix those cancerous sites that think they know better than the user). I don't want anybody to be able to touch my tabs, even the site I'm already on.

    e.g. Microsoft Outlook (web app). It seems to have this really annoying habit of opening a new page in a new tab and re-directing the old page to something useless. If only it had rel=noopener...
  • 10 stars, not 5 :D
    I LOVE the description of the extension too :D
  • ̶W̶̶̶h̶̶̶i̶̶̶l̶̶̶e̶̶̶ ̶̶̶i̶̶̶t̶̶̶ ̶̶̶d̶̶̶o̶̶̶e̶̶̶s̶̶̶ ̶̶̶h̶̶̶e̶̶̶l̶̶̶p̶̶̶ ̶̶̶h̶̶̶a̶̶̶l̶̶̶f̶̶̶ ̶̶̶t̶̶̶h̶̶̶e̶̶̶ ̶̶̶t̶̶̶i̶̶̶m̶̶̶e̶̶̶ ̶̶̶i̶̶̶t̶̶̶ ̶̶̶a̶̶̶l̶̶̶s̶̶̶o̶̶̶ ̶̶̶i̶̶̶n̶̶̶t̶̶̶r̶̶̶o̶̶̶d̶̶̶u̶̶̶c̶̶̶e̶̶̶s̶̶̶ ̶̶̶a̶̶̶ ̶̶̶g̶̶̶l̶̶̶i̶̶̶t̶̶̶c̶̶̶h̶̶̶:̶̶̶ ̶̶̶c̶̶̶l̶̶̶o̶̶̶s̶̶̶e̶̶̶d̶̶̶ ̶̶̶t̶̶̶a̶̶̶b̶̶̶s̶̶̶ ̶̶̶w̶̶̶o̶̶̶u̶̶̶l̶̶̶d̶̶̶ ̶̶̶o̶̶̶c̶̶̶c̶̶̶a̶̶̶s̶̶̶i̶̶̶o̶̶̶n̶̶̶a̶̶̶l̶̶̶l̶̶̶y̶̶̶ ̶̶̶l̶̶̶e̶̶̶a̶̶̶v̶̶̶e̶̶̶ ̶̶̶e̶̶̶m̶̶̶p̶̶̶t̶̶̶y̶̶̶ ̶̶̶s̶̶̶p̶̶̶a̶̶̶c̶̶̶e̶̶̶ ̶̶̶t̶̶̶h̶̶̶a̶̶̶t̶̶̶ ̶̶̶o̶̶̶t̶̶̶h̶̶̶e̶̶̶r̶̶̶ ̶̶̶t̶̶̶a̶̶̶b̶̶̶s̶̶̶ ̶̶̶c̶̶̶a̶̶̶n̶̶̶'̶̶̶t̶̶̶ ̶̶̶m̶̶̶o̶̶̶v̶̶̶e̶̶̶ ̶̶̶i̶̶̶n̶̶̶t̶̶̶o̶̶̶.̶̶̶

    *the only way I figured out how to reply is by editing my initial review*
    I've had this glitch for a while and was wondering what was causing it. Disabling this addon DID help. I DO, however have other addons and a heavily modded userChrome.css which, among other things, moves the tabs to the bottom. So, yes, it very well might be an extension conflict.

    So I figured out that the problem was indeed in my userChrome.css. Again, for some reason disabling this addon did help to some degree, but the bug would still occasionally return. Anyways, my mistake, I found a fix for the broken string and everything's working now. The rating changed.
    Hi Vincent, I've never ran into this issue and have not received any report about this problem by anyone else. Are you sure the culprit is not another installed add-on? Or perhaps an outdated or non-stable release of Firefox? Has it done this only since you installed DTMT and no other add-ons?

    Edit: To eleborate, DTMT does not do anything with the browser tabs themselves, it only changes a tiny portion of the HTML within tabs when pages (DOM) finish loading using a small JavaScript. I see no reason why it could have any impact on the close-tab action.

    Edit2 (response): Then unfortunately I cannot help you. I think your Firefox (configuration) just has too many things going on at once when pages finish loading and that DTMT is simply yet-another-running-script which your browser cannot take. DTMT loads it's JavaScript like any other add-on that changes page-contents such as AdBlockers etc. Sorry for the bad news :/

    Edit3 (response to *update*): Happy to hear that the mystery is solved! And thank you for adjusting your rating, much appreciated :]
  • F****ng hijacking ads! Deal with it now!
  • I tested "Don't touch" without other add-ons turned on to see how well it worked without any other help. It works on a lot of sites under Windows 7 although some seem already "counter-programmed" to then open up a pop-up since they were prevented from changing the originating page. However, on my Linux Mint machine, this add-on is completely ineffective. I know it's a lot to ask for folks to give their free time to making add-ons then test all the varied combinations out there especially since Linux is nowhere near as popular as Windows. So, as it works on Win7, I'll give three stars. However, I would suggest to the developer to prominently describe this extension as working with Windows only until there is time to adjust it for the Linux environment as well.
    Thanks for bringing this to my attention! I'm surprised that you encounter this problem since it's simply a few lines of JavaScript, perhaps Mint's Firefox has some stricter add-on settings. I will definitely take a look at this soon and get back to you on this.

    Edit: I have tested this on various Ubuntu machines with the default Firefox installed and in every test it works. I still need to test this on Mint, but so far it seems it might be a local issue. Can I ask you what Firefox and/or Mint version you are running?