James Black said the following on 1/17/2006 3:50 PM:
Please quote what you are replying to.
If you want to post a followup via groups.google.c om, don't use the
"Reply" link at the bottom of the article. Click on "show options" at
the top of the article, then click on the "Reply" at the bottom of the
article headers.
From what I understand, it is good design to give immediate feedback to whatever actions the users make.
I can agree with that, depending on your definition of immediate.
I just don't want them to assume that the click wasn't acknowledged.
Fair enough.
I don't understand how having two functions with the same name will
work, actually.
I didn't say two functions with the same name.
function function1(){
//all your visibility/innerHTML code here
window.setTimeo ut(function2,60 )
}
function function2(){
//validation code here
}
The problem you are having where the browser won't update the visual
display is because it doesn't re-display until *after* the function has
finished. By then, the form is submitted. Introducing a 60ms delay and
then executing your validation code will introduce a small enough delay
to allow the browser to update the visual screen but not enough delay to
be noticeable to the user.
--
Randy
comp.lang.javas cript FAQ -
http://jibbering.com/faq & newsgroup weekly
Javascript Best Practices -
http://www.JavascriptToolbox.com/bestpractices/
Answer:It destroys the order of the conversation
Question: Why?
Answer: Top-Posting.
Question: Whats the most annoying thing on Usenet?
Please quote what you are replying to.
If you want to post a followup via groups.google.c om, don't use the
"Reply" link at the bottom of the article. Click on "show options" at
the top of the article, then click on the "Reply" at the bottom of the
article headers.
