3 ms·
There are performance implications to adding noopener, as outlined in inhttps://jakearchibald.com/2016/performance-benefits-of-rel-noopener/ https://jakearchiba
by davidmurdoch 8y ago
There are performance implications to adding noopener, as outlined in inhttps://jakearchibald.com/2016/performance-benefits-of-rel-noopener/ https://jakearchibald.com/2016/performance-benefits-of-rel-n...
While the above link suggests noopener is beneficial to add as it will prevent the parent JS process from being paused by long running scripts in the child process, it may actually slow down the site being opened because of the additional time required to initialize the new child's process.
It also prevents sites that want to auto-close their opened tab/popup, like Facebook and other sharing sites, from being able to call `window.close` after sharing is complete.
- kentonv 8y agoNow that Chrome is moving towards strict site isolation in the wake of Spectre, that advice is probably obsolete -- Chrome will always create a new process for the new tab even if you keep the opener reference.