 | | Re: Disabling HTML form button if any changes made to an edit box? —Dan Boger
|
| | | (...) why use JS? just combine the post and preview button to one, and detect on the server if the data was changed. If it was, preview, if it wasn't (matches a CRC in a hidden form element), it posts. (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| | | |
| | | | | Re: Disabling HTML form button if any changes made to an edit box? — Todd Lehman
|
| | | | | (...) Sounds great in theory, and I think the CRC is a great fallback check if JS isn't available, and I like that the CRC method is forgiving of undone changes... But if there were only one button, what would you label it? "Preview or Post"? One (...) (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| | | | | |
| | | | | | | Re: Disabling HTML form button if any changes made to an edit box? —Dan Boger
|
| | | | | | Quoting Todd Lehman <todd@lugnet.com>: (...) I'd think label it "Preview" on the initial submit, then "Preview/Post" in the preview page. JS would be difficult to deal with undone changes, as well as confusing - "There was the post button there, and (...) (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| | | | | | |
| | | | | Re: Disabling HTML form button if any changes made to an edit box? —Brian H. Nielsen
|
| | | | (...) You don't even need the CRC. Do what you said on the message edit page about combining post & preview so that there is only preview, but then on the Message Preview page remove the whole lower section containing the message edit box, preview (...) (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| | | | |
| | | | | | Re: Disabling HTML form button if any changes made to an edit box? —Dan Boger
|
| | | | | Quoting "Brian H. Nielsen" <70401.2635@compuserve.com>: (...) while that's workable, I like being able to edit while seeing the end result that caused my edit. Meaning if I'm trying to change some formatting, I wouldn't want to have to hit back, to (...) (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| | | | | |
| | | | | | | Re: Disabling HTML form button if any changes made to an edit box? —Brian H. Nielsen
|
| | | | | | (...) That makes sense. You still don't need the CRC, even if you keep the message edit section on the Message Preview page. In the bottom messge edit section just do the same thing as suggested for the message edit page - combine the post & preview (...) (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| | | | | | |
| | | | | | | | Re: Disabling HTML form button if any changes made to an edit box? — Todd Lehman
|
| | | | | | (...) I like that idea. In fact I could even implement that immediately without any CRC or JS. That's a great idea, Brian, thanks! The top half would have only a "Post" button (and the "E-mail me a copy" checkbox) and the bottom half would have only (...) (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| | | | | | |
| | | | | | | | Re: Disabling HTML form button if any changes made to an edit box? —Brian H. Nielsen
|
| | | | | | (...) People already deal with multiple forms on a page and are used to the fact that the button they click is relevant only for the data on that form. The current Message Preview page is layed out in a manner that clearly suggests it is 2 different (...) (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| | | | | | |
| | | | | | | | Re: Disabling HTML form button if any changes made to an edit box? —Dan Boger
|
| | | | | | Quoting "Brian H. Nielsen" <70401.2635@compuserve.com>: (...) The problem is, that if you have two buttons, one says "Post" and one says "Preview", people would assume they're in the same form. I know I will. You can put multiple forms on the same (...) (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| | | | | | |
| | | | | | | | Re: Disabling HTML form button if any changes made to an edit box? — Todd Lehman
|
| | | | | | (...) I agree with Dan...especially in light of how it's always been (a single form). (...) I'm not sure. Can you point me to specific examples of "bad wrapping in the quoted text"? One thing that I am aware of, however, is a -lack- of wrapping long (...) (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| | | | | | |
| | | | | | | | Re: Disabling HTML form button if any changes made to an edit box? —Brian H. Nielsen
|
| | | | | | (...) Well, I assumed it was already 2 forms until I looked at the actual HTML. To me the horizontal rule between the 2 sections delineated the forms. If others assert they would be confused by 2 forms in this fashion what can I say? Perhaps there (...) (21 years ago, 3-Jun-03, to lugnet.publish.html)
|
| | | | | | |
| | | | | | Re: Disabling HTML form button if any changes made to an edit box? — Todd Lehman
|
| | | | (...) Except that relying on the browser's Back button is asking for trouble. Say you edit a reply, look at the preview, then go do something else, and when you return, the page is gone from your browser's cache. That would be a nasty surprise. I've (...) (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| | | | |
| | | | | | Re: Disabling HTML form button if any changes made to an edit box? —Brian H. Nielsen
|
| | | | | (...) I'll trust you on how other browsers work, you've got to maintain compatability. You can still accomplish forcing a preview before every post by removing the post button from the message edit form, leaving only the preview button. On the (...) (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| | | | | |
| | | | | | | Re: Disabling HTML form button if any changes made to an edit box? — Todd Lehman
|
| | | | | | (...) That part sounds great to me. (...) And this part also sounds great -- except for one thing: What if someone makes edits in the lower form, but then clicks the "Post" button in the top form? --Todd (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| | | | | | |
| | | | | | | | Re: Disabling HTML form button if any changes made to an edit box? —Leonard Hoffman
|
| | | | | | | (...) Todd, I was justing post a blog when i thought of something (well, saw how the blog did it) - one the page where you compose the text, it has one button that says "preview". when you hit it, you go to a page with the text, but you are unable (...) (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| | | | | | | |
| | | | | | | | | Re: Disabling HTML form button if any changes made to an edit box? — Todd Lehman
|
| | | | | | | | (...) I think that might make more work for the user than is strictly necessary. If the server detects changes automatically (or if JS disabled the "Post" button automatically), then it eliminates a step. --Todd (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| | | | | | | | |
| | | | | | | | Re: Disabling HTML form button if any changes made to an edit box? —Brian H. Nielsen
|
| | | | | | (...) Maybe that's what they intend to do. They may start to edit the message and then change their mind. If you are doing JS or CRC to check for changes in the edit box then you also need a way to reset it if edits are started and then decided (...) (21 years ago, 3-Jun-03, to lugnet.publish.html)
|
| | | | | | |
| | | | | | Re: Disabling HTML form button if any changes made to an edit box? —William R. Ward
|
| | | | (...) Yes, you don't want to use the browser's Back button. But you can easily add an "Edit" button to the preview page, which takes you back to an edit page with the changes intact. (...) Yes, and Mozilla doesn't preserve the contents of each frame (...) (21 years ago, 2-Jun-03, to lugnet.publish.html)
|
| | | | |
