Yes. In that case SH is enough to get all the urls visited. However, SH
does not persist between sessions. The embeddor has to do that.
Chak Nanga wrote:
> Forgot to add this earlier....
>
> If someone's writing an app with just a single instance of an embedded browser, then
> your per session nsIBrowserHistory interface would suffice to implement the
> Communicator like histrory UI.
>
> I was thinking of a case where the app allows multiple browser windows(sessions)
>
> Chak
>
> Chak Nanga wrote:
>
>
>> Radha Kulkarni wrote:
>>
>>
>>> <---Snip---->
>>>
>>> Please note that all this information is for the currently embedded browser
>>> object ie., session history only. No tie up with global history is
>>> provided here.
>>>
>>> <----Snip>
>>
>> Hi Radha,
>>
>> Are there plans to expose an interface to the global history ? (with methods
>> similar to your proposed per session nsIBrowserHistory interface)
>>
>> I'm thinking of embeddors who may be interested in implementing a UI similar to
>> the one which the Communicator/Tools/History menu item brings up in Netscape 4.x?
>>
>> Thanks
>> Chak
