Subject:
|
Re: Disabling HTML form button if any changes made to an edit box?
|
Newsgroups:
|
lugnet.publish.html
|
Date:
|
Mon, 2 Jun 2003 14:20:19 GMT
|
Viewed:
|
2486 times
|
| |
|
|
In lugnet.publish.html, Dan Boger wrote:
> 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.
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 way to avoid that ambiguity could be to label the submit button "Post" by
default and then relabel it "Preview" if any of the text changes. That still
requires JS, of course, but should degenerate acceptably if JS isn't
available...it would just need to output a note or something at the top saying
that the message hadn't been posted yet because it had changed.
What do you think? Is there a disambiguous static name for the Preview/Post
button or would relabeling it dynamically be the least confusing?
--Todd
|
|
Message has 1 Reply:
Message is in Reply To:
19 Messages in This Thread:
   
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
