In what way is the XulPlanet documentation out of date? I've heard a number of people mention it, but no-one has given any examples. I can't fix it if I don't know what's wrong with it.

If anybody wants to deploy a stand alone xul app he will be in trouble, there is no docs about making that simple thing. Most info are about deploying an xul app as a browser extension, but that is not what *all* people wants. This seems to be a long-term illness of mozilla as a platform, this situation is not going to change soon as this is rather a dificult task as I understand. One gets even more dissappointed when see that projects like the Komodo IDE uses some strage hacks to get the hole thing look like another app, in the end they included the entire mozilla browser in order to make the thing work, which adds a lot of overhead indeed. Not every project have the resources to hack mozilla at that level, and the mozilla comunity seems to be fine with the current state of pushing nothing but the web browser, but people like me really appreciate the whole platform, unfortunately this 'little' issue makes me give up too and think about leaving the mozilla platform for a while... well not at all I will be here some more time until I finish my current project. Anyway XUL is the greatest gui technology I ever used.

Well Mozilla does warn you by default if you go back or reload a page that'll trigger a form submission, so it's already got a partial defence against that.

Secondly it is possible (although not the most fun task!) to write server-side apps defensively so that they will ignore, discard or query duplicate form submissions, and really this is the only way to do it that you can be sure of.

If you rely on any browser based mechanism to deter duplicate form submissions you're relying on users using specific versions of specific browsers that implement the specific features you want, and in the real world that is rarely realistic.