I guess Everything *could* change the action parameter, but it doesn't work that way. Instead, any page element that contains a form is supposed to call a startform htmlcode or wrap itself in a formcontainer. These just provide a hidden node_id parameter with the current node id. Otherwise, forgetful Everything developers will spend a lot of time wondering why they keep getting the default node during form debugging. (Explained without a <emphasis>hint</emphasis> of bitterness.)

As for ignoring GET parameters when a form is POSTed, that's really not an option. Everything uses CGI. :) In fact, I'm not sure exactly what GET parameters in an action attribute are supposed to accomplish. Nor am I certain what a browser refresh/reload is supposed to do. Time for a trip to the relevant RFCs, perhaps.

My inclination is to say that any user agent which doesn't accurately recreate the information sent to the server when reloading the current page is broken. If your web browser uses what's displayed in the Location bar instead of what was sent via POST, that counts as broken. :)