Infocatcher
Infocatcher
Oh, the same issue without `@run-at document-start`: ``` js // ==UserScript== // @name Test Scriptify #2 // @namespace dev/null // @include https://github.com/* // @version 0.1 // @grant none // ==/UserScript==...
Test: ``` js var c = 100; var timerDelay = 0; var testDelay = 300; var ok = 0; var failed = 0; var tester = asyncTester(); tester.next(); function asyncTester()...
Additional tests: ``` js _log("setTimeout()"); setTimeout(function() { _log("setTimeout() done"); }, 0); _log("mainThread.dispatch()"); Services.tm.mainThread.dispatch(function() { _log("mainThread.dispatch() done"); }, 0); _log("postMessage()"); delayed(function() { _log("postMessage() done"); }); _log("addTab()"); gBrowser.selectedTab = gBrowser.addTab("about:"); _log("addTab() done");...
Should works fine since Scriptify 0.2.6: https://addons.mozilla.org/addon/scriptify/versions/0.2.6 Don't use frame managers when e10s is disabled, as it leads to spinning the event loop on the main thread. But only with...
Strange, works fine for me. This is probably conflict with another extension. So, how this works on new Firefox profile? Also please set extensions.privateTab.debug = true on about:config page, open...
> tahani5/Private_Tab@7075ece @tahani5, thanks! Updated: f69c4ac005ccb05b735cac26cdda6939f6074c0d (I leaved name unchanged) Also please translate other new strings: /locale/ar/pt.properties
> Of course, with my pleasure > > da67f4cd1654fdf3417e4e9f502220700fbe5501 Thanks, updated: 529f29a80cbac082c54c17e40879afa8c83098cf And two not yet translated lines: /locale/ar/pt.properties#L27: ```properties taskBarOpenNewPrivateTabDesc=Open a new tab in private browsing mode. ``` /locale/ar/pt.properties#L30:...
> The current underline is not very obvious, especially on a high-res screen, so it would be good if there was an option to make Private Tabs stand out more...
> And here is my workaround (for Linux): Interesting, thanks for investigation. But the main problem is to prevent things like ``` js var win = window.open("p" + location.href); //...
> So for clarification, will this ever be an option? Opening private tabs from non-private tabs? May be... But only if will work for user actions and not for page...