Closed Bug 100993 Opened 23 years ago Closed 23 years ago

Update nsIHistoryEntry and nsIHistory...

Categories

(Core Graveyard :: Embedding: APIs, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED
mozilla1.0

People

(Reporter: chak, Assigned: radha)

Details

Attachments

(1 file, 1 obsolete file)

nsIHistoryEntry and nsIHistory are currently marked as FROZEN.

They need to be updated to bring them in line with the interface freeze
guidelines at http://www.mozilla.org/projects/embedding/EmbedInterfaceFreeze.html

The same document also gives the issues to be addressed for these particular
interfaces, which are:

nsISHistory:
  * Remove #include for nsIFactory
  * Change #includes to forward declarations for nsIHistoryEntry and
nsIHistoryListener


nsIHistoryEntry:
  * Change the #include of nsIURI.idl into a forward declaration
QA Contact: mdunn → depstein
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.0
Attached patch Initial patch (obsolete) — Splinter Review
Should we be using "PR_TRUE" and "PR_FALSE" in the comment section for the
following attribute[It currently uses "true"/"false" as the return value]

>>>> readonly attribute boolean isSubFrame;

Other than that r=chak
 
Comment on attachment 51301 [details] [diff] [review]
Updated patch

sr=alecf
Attachment #51301 - Flags: superreview+
Attachment #50767 - Attachment is obsolete: true
in IDL, it's more appropriate to refer to 'true' vs 'false' rather than PR_TRUE
vs. PR_FALSE (which are more NSPR concepts than IDL)
Fix checked in. 
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
verified against mozilla 0.9.4+ Gecko 20011001:
In nsISHistory.idl:
* #include of nsIFactory was removed
* #includes were changed to forward declations ("interface xxx") for
nsIHistoryEntry and nsIHistoryListener.
In nsIHistoryEntry.idl:
* changed #include to forward declaration of nsIURI.idl.
In nsSHistory.cpp
* code added to RemoveSHistoryListener()

#includes added to various header files.
Status: RESOLVED → VERIFIED
Why was this frozen with PurgeHistory() (as opposed to purgeHistory())?
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: