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 / 305
304  |  306
Subject: 
Re: Disabling HTML form button if any changes made to an edit box?
Newsgroups: 
lugnet.publish.html
Date: 
Mon, 2 Jun 2003 18:28:09 GMT
Viewed: 
2511 times
  
Quoting "Brian H. Nielsen" <70401.2635@compuserve.com>:
In lugnet.publish.html, Todd Lehman wrote:
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.*

   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.

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 page, as long as they're obviously seperated.
But in this case, you're putting two forms with the SAME function - extreamly
confusing.  Bad UI design.

Dan

PS.  Is the really bad wrapping in the quoted text a result of the new
formatting features?  Any chance that'll be fixed?



--
Dan Boger
dan@peeron.com



Message has 1 Reply:
  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)

Message is in Reply To:
  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)

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
    

Custom Search

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