I don't think javascript is necessary for the server to simply not emit the HTML tags that would denote the button. Straight Perl should be sufficient.
On the other hand, it's not the submit button that's the problem. As someone else points out, it's the refresh button provided by the browser itself that is at issue.
The solution is to disallow multiple distinct posts to an area by the same monk within a time window (something I'd like to see to prevent flooding), or to disallow root nodes from the same monk that have duplicate names (a solution I'd also like to see, since it makes for better searches when the list isn't populated by the same title over and over).
In any case, I don't think hiding submit is a good idea since often a post will be gummed up and require a quick fix. The lack of a submit button would make it hard to fix such an error. | [reply] |