Closed
Bug 842618
Opened 10 years ago
Closed 10 years ago
SeaMonkey contains PrivateBrowsingUtils.jsm, but it throws an exception if used
Categories
(SeaMonkey :: Preferences, defect)
SeaMonkey
Preferences
Tracking
(Not tracked)
RESOLVED
FIXED
seamonkey2.19
People
(Reporter: morac, Assigned: philip.chee)
References
Details
Attachments
(2 files)
1.84 KB,
patch
|
iannbugzilla
:
review+
|
Details | Diff | Splinter Review |
2.04 KB,
patch
|
philip.chee
:
review+
|
Details | Diff | Splinter Review |
The trunk (2.18a1 branch) version of SeaMonkey added the resource://gre/modules/PrivateBrowsingUtils.jsm, but because SeaMonkey doesn't support Private Browsing, referencing PrivateBrowsingUtils.permanentPrivateBrowsing throws the following exception: Tue Feb 19 2013 11:58:51 Error: NS_ERROR_UNEXPECTED: Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getBoolPref] Source file: resource://gre/modules/PrivateBrowsingUtils.jsm Line: 31 since the browser.privatebrowsing.autostart preference does not exist in SeaMonkey. My add-on assumes that if PrivateBrowsingUtils.jsm exists, then it works. As such it is not broken in the nightly SeaMonkey loads until I add try/catches around all calls to PrivateBrowsingUtils.jsm. If Private Browsing isn't supported, SeaMonkey should not include the PrivateBrowsingUtils.jsm module.
![]() |
Assignee | |
Comment 1•10 years ago
|
||
> The trunk (2.18a1 branch) version of SeaMonkey added the resource://gre/modules
> /PrivateBrowsingUtils.jsm, but because SeaMonkey doesn't support Private Browsing,
> referencing PrivateBrowsingUtils.permanentPrivateBrowsing throws the following
> exception:
Experimental private browsing was checked in to comm-central about three or four days ago so per window Private Browsing is supported. We could of course add "pref("browser.privatebrowsing.autostart", false);" to our browser-prefs.js
OS: Windows XP → All
Hardware: x86 → All
![]() |
Assignee | |
Updated•10 years ago
|
Component: General → Preferences
![]() |
Assignee | |
Comment 2•10 years ago
|
||
This pref adds the "browser.privatebrowsing.autostart" pref to our browser-prefs.js for extension-compat
Assignee: nobody → philip.chee
Status: NEW → ASSIGNED
Attachment #717525 -
Flags: review?(neil)
Attachment #717525 -
Flags: review?(iann_bugzilla)
Attachment #717525 -
Flags: review?(iann_bugzilla) → review+
![]() |
Assignee | |
Comment 3•10 years ago
|
||
Pushed to comm-central: http://hg.mozilla.org/comm-central/rev/ddd02164f9f7
Target Milestone: --- → seamonkey2.19
![]() |
Assignee | |
Comment 4•10 years ago
|
||
Michael; Just to note that with this patch PrivateBrowsingUtils won't throw. But nothing in SeaMonkey ever sets this to true.
Reporter | ||
Comment 5•10 years ago
|
||
(In reply to Philip Chee from comment #4) > Michael; Just to note that with this patch PrivateBrowsingUtils won't throw. > But nothing in SeaMonkey ever sets this to true. That's fine.
Comment 6•10 years ago
|
||
(In reply to Philip Chee from comment #4) > Michael; Just to note that with this patch PrivateBrowsingUtils won't throw. > But nothing in SeaMonkey ever sets this to true. And if someone does set it to true then SeaMonkey will probably stop working properly.
Comment 7•10 years ago
|
||
Note bug 845341. It was a bug in the toolkit code to assume this pref always exists.
![]() |
Assignee | |
Comment 8•10 years ago
|
||
Note to self: Back out this patch once Bug 845341 is fixed [PrivateBrowsingUtils.permanentPrivateBrowsing can throw if the autostart pref does not exist]
Depends on: 845341
![]() |
Assignee | |
Comment 9•10 years ago
|
||
Now that Bug 845341 is fixed this can be backed out. Backout changeset: http://hg.mozilla.org/comm-central/rev/8b8ff0fc1c16
Attachment #718969 -
Flags: review+
![]() |
Assignee | |
Updated•10 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
![]() |
Assignee | |
Comment 10•10 years ago
|
||
Comment on attachment 717525 [details] [diff] [review] Patch v1.0 add browser.privatebrowsing.autostart to browser-prefs.js Cancelling review request
Attachment #717525 -
Flags: review?(neil)
You need to log in
before you can comment on or make changes to this bug.
Description
•