Closed
Bug 615219
Opened 14 years ago
Closed 12 years ago
[ChatZilla] Start using nsIGlobalHistory2, maybe stop support for nsIGlobalHistory
Categories
(Other Applications :: ChatZilla, defect)
Other Applications
ChatZilla
Tracking
(blocking-seamonkey2.1 -, seamonkey2.12 wontfix, seamonkey2.13 affected, seamonkey2.14 affected, seamonkey2.15 fixed)
People
(Reporter: sgautherie, Assigned: Gijs)
References
(Blocks 1 open bug, )
Details
(Whiteboard: [cz-0.9.89])
Attachments
(1 file, 1 obsolete file)
3.29 KB,
patch
|
bugzilla-mozilla-20000923
:
review+
|
Details | Diff | Splinter Review |
(Noticed while investigating bug 603031.) http://mxr.mozilla.org/mozilla-central/source/docshell/base/nsIGlobalHistory.idl { 42 * @status DEPRECATED. This interface is still accepted, but new 43 * implementations should use nsIGlobalHistory2. 52 /** 53 * addPage 54 * Add a page to the history 55 * 56 * @param aURL the url to the page 57 */ 58 59 void addPage(in string aURL); } http://mxr.mozilla.org/mozilla-central/source/docshell/base/nsIGlobalHistory2.idl { 58 /** 59 * Add a URI to global history 60 * 61 * @param aURI the URI of the page 62 * @param aRedirect whether the URI was redirected to another location; 63 * this is 'true' for the original URI which is 64 * redirected. 65 * @param aToplevel whether the URI is loaded in a top-level window 66 * @param aReferrer the URI of the referring page 67 * 68 * @note Docshell will not filter out URI schemes like chrome: data: 69 * about: and view-source:. Embedders should consider filtering out 70 * these schemes and others, e.g. mailbox: for the main URI and the 71 * referrer. 72 */ 73 void addURI(in nsIURI aURI, in boolean aRedirect, in boolean aToplevel, in nsIURI aReferrer); } I don't know whether nsIGlobalHistory support needs to be kept for the older application versions we care about now.
Reporter | ||
Comment 1•14 years ago
|
||
Per bug 615213 comment 2, this is now major :-<
Severity: normal → major
Depends on: 615213
Reporter | ||
Comment 2•14 years ago
|
||
"blocking-seamonkey2.1=?": if not blocking then surely wanted...
blocking-seamonkey2.1: --- → ?
Comment 3•14 years ago
|
||
According to MXR nsIGlobalHistory2 is available all the way back to Mozilla 1.7 and the Aviary branch. http://mxr.mozilla.org/mozilla1.7/find?string=nsIglobalHistory&tree=mozilla1.7&hint= http://mxr.mozilla.org/aviary101branch/find?string=nsIglobalHistory&tree=aviary101branch&hint= nsIGlobalHistory2 checked in 2004-02-10 18:09 https://bugzilla.mozilla.org/show_bug.cgi?id=224829#c37 According to Bug 224829 Comment 37 there was a backward compatibility adapter that existed only because of Chatzilla which chatzilla apparently never used :P > nsIGlobalHistory2->nsIGlobalHistory > (nsGlobalHistory2Adapter, for use by extensions such as chatzilla which want > nsIGlobalHistory) But grepping though the Chatzilla source code it looks like just a SMOP to change the callers.
Reporter | ||
Comment 4•14 years ago
|
||
Robert, can it be expected that you work on this bug or is it helpwanted?
Comment 5•13 years ago
|
||
As long as nsIGlobalHistory is still present in 2.1, I'm not even marking this as wanted; since it is a 3rd party extension, we happen to ship with. But I would like to see this as well.
blocking-seamonkey2.1: ? → -
Assignee | ||
Comment 6•12 years ago
|
||
nsIGlobalHistory2 has been around since 2007. As we've updated compat requirements to beyond that date, I believe it's safe to just switch wholesale. This will also allow us to release a Fx15-compatible version to AMO.
Assignee: rginda → gijskruitbosch+bugs
Status: NEW → ASSIGNED
Attachment #658241 -
Flags: review?(silver)
Assignee | ||
Comment 7•12 years ago
|
||
(In reply to Gijs Kruitbosch from comment #6) > since 2007. Excuse me, that was supposed to be *at least* 2007 - I didn't bother checking CVS as it was in the original hg import.
Reporter | ||
Comment 8•12 years ago
|
||
Comment on attachment 658241 [details] [diff] [review] Patch Does this patch actually work? I mean "global-history;1" and "addPage()"...
Assignee | ||
Comment 9•12 years ago
|
||
Comment on attachment 658241 [details] [diff] [review] Patch (In reply to Serge Gautherie (:sgautherie) from comment #8) > Comment on attachment 658241 [details] [diff] [review] > Patch > > Does this patch actually work? I mean "global-history;1" and "addPage()"... Fair point. I totally blame the AMO warnings that claim "You can use nsIGlobalHistory2 instead". Sigh. Proper patch coming tonight.
Attachment #658241 -
Flags: review?(silver)
Assignee | ||
Updated•12 years ago
|
Attachment #658241 -
Attachment is obsolete: true
Assignee | ||
Comment 10•12 years ago
|
||
This has the benefit of actually being tested and stuff. AFAICT this should work on everything we still support.
Attachment #658568 -
Flags: review?(silver)
Comment 11•12 years ago
|
||
Comment on attachment 658568 [details] [diff] [review] Patch [checked in] Review of attachment 658568 [details] [diff] [review]: ----------------------------------------------------------------- ::: xul/content/static.js @@ +945,5 @@ > destroyPrefs(); > } > > + > +function addURLToHistory(url, referer) { Nit: Braces go on new lines (and elsewhere). :) @@ +947,5 @@ > > + > +function addURLToHistory(url, referer) { > + if (client.globalHistory) { > + referer = referer ? client.iosvc.newURI(referer, "UTF-8", null) : null; The referer is never used, though I guess it might be handy; did you have anything in mind here or just future utility?
Attachment #658568 -
Flags: review?(silver) → review+
Assignee | ||
Comment 12•12 years ago
|
||
Checked in with nits, http://hg.mozilla.org/chatzilla/rev/8e70231eca3d . (In reply to James Ross from comment #11) > The referer is never used, though I guess it might be handy; did you have > anything in mind here or just future utility? Pretty much just futureproofing (I know, I know).
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•12 years ago
|
Attachment #658568 -
Attachment description: Patch → Patch [checked in]
Reporter | ||
Updated•12 years ago
|
status-seamonkey2.12:
--- → wontfix
status-seamonkey2.13:
--- → affected
status-seamonkey2.14:
--- → affected
status-seamonkey2.15:
--- → fixed
Updated•12 years ago
|
Whiteboard: [cz-0.9.89]
You need to log in
before you can comment on or make changes to this bug.
Description
•