Closed
Bug 349961
Opened 19 years ago
Closed 19 years ago
Remove use of explicit native wrappers in session restore service
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: Gavin, Assigned: zeniko)
References
Details
Attachments
(1 file, 1 obsolete file)
5.40 KB,
patch
|
dietrich
:
review+
mtschrep
:
approval1.8.1-
|
Details | Diff | Splinter Review |
Now that bug 345991 is fixed, there should be no need to use explicit wrappers in the session restore components.
Comment 1•19 years ago
|
||
wrapper removal. works fine on trunk, text is re/stored as usual.
Assignee | ||
Comment 2•19 years ago
|
||
This slightly more comprehensive patch additionally removes the unnecessary and non-working code paths for about:config and doesn't store two references to text areas where one is sufficient.
Dietrich: If you agree with these changes, please re-assign the bug to me and check it in on Trunk for testing. Thanks.
Attachment #236612 -
Flags: review?(dietrich)
Updated•19 years ago
|
Attachment #236612 -
Flags: review?(dietrich) → review+
Updated•19 years ago
|
Attachment #235196 -
Attachment is obsolete: true
Attachment #235196 -
Flags: review?(mconnor)
Assignee | ||
Updated•19 years ago
|
Assignee: dietrich → zeniko
Status: ASSIGNED → NEW
Whiteboard: [checkin needed]
Updated•19 years ago
|
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Whiteboard: [checkin needed]
Assignee | ||
Comment 3•19 years ago
|
||
Comment on attachment 236612 [details] [diff] [review]
fix (removing non-working code paths for about:config)
Drivers: This low-risk patch removes a broken code path (tracked by bug 350718) and all references to XPCNativeWrappers from SessionStore.
It'd be nice to have in order not to make extension authors looking through the included components for inspiration think that explicit native wrappers are still required.
Attachment #236612 -
Flags: approval1.8.1?
Comment 4•19 years ago
|
||
Can we confirm that these objects are getting properly wrapped w/o the explicit use of native wrappers?
Assignee | ||
Comment 5•19 years ago
|
||
(In reply to comment #4)
> Can we confirm that these objects are getting properly wrapped w/o the explicit
> use of native wrappers?
The native wrappers are now guaranteed by bug 345991 and have led to bug 350718 (about:config's filter is no longer saved/restored because the relevant code required the absence of a native wrapper). So yes, we can confirm this.
Are there any benefits to this other than code cleanup?
Comment 7•19 years ago
|
||
Comment on attachment 236612 [details] [diff] [review]
fix (removing non-working code paths for about:config)
We are closing in on the RC1 code freeze and are only taking bugs that match the criteria for 181 approvals:
http://developer.mozilla.org/devnews/index.php/2006/08/28/firefox-2gecko-181-approvals-2/
Since this is just code cleanup we are going to skip. If there is another reason why we should take for the branch please note/re-nom.
Attachment #236612 -
Flags: approval1.8.1? → approval1.8.1-
![]() |
||
Comment 8•19 years ago
|
||
For the XPCNativeWrapper parts, not really. At least not that I can think of.
You need to log in
before you can comment on or make changes to this bug.
Description
•