- From: Edmund Lai <edmund.lai@gmail.com>
- Date: Thu, 1 Jul 2004 14:25:03 -0700
All I am asking is that if the browser saves the page, fire a onSave event first. If they don't support saving the page, then the onSave event will not fire. On Thu, 01 Jul 2004 17:14:58 +0200, Anne van Kesteren (fora) <fora at annevankesteren.nl> wrote: > > > > Every browser has a save page as command, however last time I looked > > at opera and safari, they just save the original source, with DOM and > > even more with WF2, the content is a lot more dynamic, and saving the > > source won't do. Mozilla does try to save the current content, but has > > bugs on it. It also does not save what you typed into the text fields. > > > > They should fix this regardless of WF2. > > > > However, bug fix is not sufficient because we have Javascript > > variables that may have changed. > > > > If we have a onSave event, then the application can move these > > variables to some place where it will be saved when the web page is > > actually being saved. > > I think this is outside the scope of this specification. Whether or not > a browser will let you save a page is up to the browser vendor, how they > support is up to them as well. > > > -- > Anne van Kesteren > <http://annevankesteren.nl/> > >
Received on Thursday, 1 July 2004 14:25:03 UTC