Closed Bug 1218143 Opened 9 years ago Closed 9 years ago

Firefox 42.0b9 broke "private:" pseudo-protocol used by the Private Tab extension

Categories

(Firefox :: Extension Compatibility, defect)

42 Branch
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: 08xjcec48, Unassigned)

References

Details

(Keywords: addon-compat, regression)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:42.0) Gecko/20100101 Firefox/42.0 Build ID: 20151022152545 Steps to reproduce: Installed https://addons.mozilla.org/firefox/addon/private-tab/ Typed private:http://example.org/ in the address bar and pressed enter. Actual results: Nothing. Expected results: The tab should be converted by the Private Tab extension (https://addons.mozilla.org/firefox/addon/private-tab/). Its private: pseudo-protocol worked fine until the Firefox 42 Beta 9 update.
If it still worked in 42.0b8, then it's still likely due to bug 1214122 / http://hg.mozilla.org/releases/mozilla-beta/rev/e1261e250e85 Jorge, should this bug be closed as invalid and the developer be informed about the issue? From the browser console: A promise chain failed to handle a rejection. Did you forget to '.catch', or did you forget to 'return'? See https://developer.mozilla.org/Mozilla/JavaScript_code_modules/Promise.jsm/Promise Date: Sun Oct 25 2015 17:30:38 GMT+0100 Full Message: Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIWebNavigation.loadURIWithOptions] Full Stack: JS frame :: chrome://browser/content/browser.js :: _loadURIWithFlags :: line 11704 JS frame :: chrome://browser/content/tabbrowser.xml :: loadURIWithFlags :: line 6354 JS frame :: chrome://privatetab/content/patcher.jsm :: wrapper :: line 39 JS frame :: chrome://browser/content/tabbrowser.xml :: loadURIWithFlags :: line 3709 JS frame :: chrome://browser/content/utilityOverlay.js :: openLinkIn :: line 334 JS frame :: chrome://browser/content/utilityOverlay.js :: openUILinkIn :: line 188 JS frame :: chrome://browser/content/urlbarBindings.xml :: handleCommand/continueOperation/loadCurrent :: line 377 JS frame :: chrome://browser/content/urlbarBindings.xml :: continueOperation :: line 418 JS frame :: chrome://browser/content/urlbarBindings.xml :: handleCommand/< :: line 359 JS frame :: chrome://browser/content/urlbarBindings.xml :: _canonizeURL/< :: line 485 JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: Handler.prototype.process :: line 934 JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: this.PromiseWalker.walkerLoop :: line 813 JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: this.PromiseWalker.scheduleWalkerLoop/< :: line 747 native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0
Flags: needinfo?(jorge)
Sebastian, I've already reported it here: https://github.com/Infocatcher/Private_Tab/issues/190 But if you close this issue, please tell the developer there what exactly he must do to fix it.
Blocks: 1214122
Component: Untriaged → Extension Compatibility
Summary: Firefox Firefox 42.0b9 broke "private:" pseudo-protocol used by the Private Tab extension → Firefox 42.0b9 broke "private:" pseudo-protocol used by the Private Tab extension
It's likely and invalid bug, but someone should confirm this isn't problem in Firefox. It looks like the dev was already notified via github.
Flags: needinfo?(jorge)
(In reply to Jorge Villalobos [:jorgev] from comment #3) > It's likely and invalid bug, but someone should confirm this isn't problem > in Firefox. It looks like the dev was already notified via github. As I noticed on GitHub, this is strange: looks like all already fixed in latest aurora and nightly. But what will be in the next beta/release?
Seems to be https://bugzilla.mozilla.org/show_bug.cgi?id=1214786#c24 which will be included in the Firefox 42 RC builds which should be releases in ~24 hours.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Depends on: 1214786
Resolution: INVALID → FIXED
You need to log in before you can comment on or make changes to this bug.