Code: Select all
WARNING: content window passed to PrivateBrowsingUtils.isWindowPrivate. Use isContentWindowPrivate instead (but only for frame scripts). pbu_isWindowPrivate@resource://gre/modules/PrivateBrowsingUtils.jsm:25:14 @about:privatebrowsing:40:12
Could it be that there is a bug – or simply a contraindication – in Pale Moon's private browsing that would explain why the Private Tab add-on is having trouble even though it does work as expected?
I'm using PM 28.0.1 64bit on Linux.
Background (for those who don't know "Private Tab"): It allows one to have both private and regular tabs in the same browser window. You can have a shortcut key to open such a private tab (just like Ctrl+T opens a regular tab, I had Alt+P to open a private one) and it also allows you to put the string "private:" in front of a URL in a bookmark, for those sites you want to make sure you'll always open in a private tab.
I had been using it for a decade in an old version of FF on Windows and it worked great, so I would miss it immensely.