To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.publish.htmlOpen lugnet.publish.html in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Publishing / HTML / 304
303  |  305
Subject: 
Re: Disabling HTML form button if any changes made to an edit box?
Newsgroups: 
lugnet.publish.html
Date: 
Mon, 2 Jun 2003 17:27:10 GMT
Viewed: 
7380 times
  
In lugnet.publish.html, Todd Lehman wrote:
> In lugnet.publish.html, Brian H. Nielsen wrote:
> > 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 buttons so that there is only preview.
> 
> 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 a "Preview" button.
> 
> > Now the only place that the post button appears in in the top half of the
> > Message Preview page.  If the message in the bottom section is edited it
> > still has to be previewed.
> 
> But what if someone edits in the bottom area and then clicks "Post" in the top
> area?  If the top and half are different forms, then the user would lose the
> edits in the bottom half.  If the top and bottom half are the same form, then
> the user would be able to post without previewing.
> 
> I think the top and bottom half have got to be the same form, and the "Post"
> button still needs to be grayed out if editing changes are made.  And with
> the fallback (in case JS isn't available to gray out the "Post" button) of
> either a quick CRC check between the new content, or a string-equal comparison
> of the old and new content.*
> 
> --Todd

   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 forms (even if the HTML is not coded that way).  I don't think
people will be confused in the least, but go with what makes you happy.  The JS
or CRC will make it idiot proof.

Brian H. Nielsen



Message has 1 Reply:
  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 (...) (23 years ago, 2-Jun-03, to lugnet.publish.html)

Message is in Reply To:
  Re: Disabling HTML form button if any changes made to an edit box?
 
(...) 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 (...) (23 years ago, 2-Jun-03, to lugnet.publish.html)

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
    

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR