did you check multizilla? maybe it has that.
psmith wrote:
Neither option would allow any reloading initiated by the website. I
suppose I left out a default option for not altering the web site's
reloading at all.* THANK YOU FOR IMPLEMENTING THIS FOR ME SOON!*
psmith wrote:
Actually I did post this on Bugzilla. It is #109507, been there for
about 3 months, but no one seems to have addressed it yet. I think it's
a very useful idea to have scheduled reloading of tabs (and standalone
browser windows) as it would be very useful in active
Netscape Basher wrote:
psmith typed:
Sören Kuklau wrote:
On 3/9/2002 2:26 PM, psmith apparently wrote exactly the following:
Neither option would allow any reloading initiated by the website.
I suppose I left out a default option for not altering the web
site's reloading at all.
ahmetaa wrote:
did you check multizilla? maybe it has that.
psmith wrote:
Neither option would allow any reloading initiated by the website. I
suppose I left out a default option for not altering the web site's
reloading at all.* THANK YOU FOR IMPLEMENTING THIS FOR ME SOON!*
I
On 3/9/2002 2:26 PM, psmith apparently wrote exactly the following:
Neither option would allow any reloading initiated by the website. I
suppose I left out a default option for not altering the web site's
reloading at all.
Why not post this at bugzilla, or at least in npm.wishlist?
Sören Kuklau wrote:
On 3/9/2002 2:26 PM, psmith apparently wrote exactly the following:
Neither option would allow any reloading initiated by the website. I
suppose I left out a default option for not altering the web site's
reloading at all.
Why not post this at bugzilla, or at least
psmith typed:
Sören Kuklau wrote:
On 3/9/2002 2:26 PM, psmith apparently wrote exactly the following:
Neither option would allow any reloading initiated by the website. I
suppose I left out a default option for not altering the web site's
reloading at all.
Why not post this at
