| If you are on a text field and press enter and the form submits, the | behavior is inconsistent between browsers. Some pass the first submit
Now I see. I expect your hidden-field trick solves this nicely. We do a similar thing with our FormKit to allow the servlets to easily handle when there are multiple forms on one page (we store a <input type="hidden" name="__formid__" value="2" /> type of thing). | I was under the impression that query strings for form actions wasn't | exactly legal HTML. This would/could cause problems with action="get" It may not be, and you're right, if the form is of type "get", it doesn't work, but it's working fine for POST, and since webkit does the work of combining POST and GET vars into response().fields(), it's easy. It's certainly not a technique that should be canonized into webkit or anything, but it does work. I have yet to find a browser that doesn't like it. HTML forms are just a nasty way to make an application, and for some odd reason, the W3C/HTML folks never seem to improve them. | I've looked at these, but have yet to invest the time necessary to grok | them completely. Well, speaking at least for my own project, I'd be happy to answer any questions, and I'd like to think that the supplied docs are more than sufficient for someone with your obvious experience. Then again, sometimes it's better to just roll-your-own. | The only problem that I have with the current action handling is that | the "old style" is handled differently that the _action_methodName | style. My proposal is that the "old style" section is changed into a I agree. If it's not going to be removed, it should at least be made to conform to the same handling style. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
