Nickolay Ponomarev wrote: > On 9/7/07, Matthew Gertner <[EMAIL PROTECTED]> wrote: >> Nickolay Ponomarev wrote: >>> The JS code in nearly all extensions does some initialization on >>> application startup or when a window it overlays loads. It's >>> impossible to implement installation-without-restart for extensions >>> without changes on their end. >> Why not simply reload all chrome that is affected by relevant overlays? > > Reloading chrome means losing any changes that were made to it by > scripts, as well as the script's state.
Right, well you would rerun all the relevant scripts when you reload the overlays. Basically I'm proposing an intermediate stage which would be basically restarting Firefox but without the restarting Firefox part (i.e. no need to quit and restart the actual OS process). > >> A second phase might be to include hints in overlays about what they >> might affect (reducing the scope of what has to be reloaded) and/or >> deducing this programatically. This strikes me as far better than having >> to restart Firefox. > > I don't see how it's different from document.loadOverlay. Can you explain in a bit more detail how your solution using document.loadOverlay would work? Matt _______________________________________________ dev-tech-xpcom mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-xpcom
