 | | Re: Disabling HTML form button if any changes made to an edit box?
|
|
(...) 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: // and ** vs {} and [] (was: testing in rtl...)
|
|
(...) CNews. (...) Doesn't that look a bit redundant? /italics/ and *boldface* What do underlined underlines look like? Like this?-- _N_ew _E_ngland _L_EGO _U_sers _G_roup Not sure how either any of those are an improvement. --Todd (21 years ago, 3-Jun-03, to lugnet.publish, lugnet.admin.nntp, FTX)
|
| |
| | Re: Disabling HTML form button if any changes made to an edit box?
|
|
(...) 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)
|
| |
| | Re: Disabling HTML form button if any changes made to an edit box?
|
|
(...) 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: // and ** vs {} and [] (was: testing in rtl...)
|
|
(...) What NNTP server do you use? I was under the impression that it was written in Perl itself. [...] (...) How about a different interpretation - // and ** (and don't forget __ for underlining) might not be interpreted the same as the {} and [] (...) (21 years ago, 2-Jun-03, to lugnet.publish, lugnet.admin.nntp)
|
| |
| | Re: Disabling HTML form button if any changes made to an edit box?
|
|
(...) 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?
|
|
(...) 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?
|
|
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?
|
|
(...) 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?
|
|
(...) 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)
|
