HTML & JavaScript Loader
November 14th, 2009 — adminIn this program just change the source of iframe and your loading.gif will show upto that time when page will not upload finally.
For Demo Click Here
Download Script Click Here
In this program just change the source of iframe and your loading.gif will show upto that time when page will not upload finally.
For Demo Click Here
Download Script Click Here
First of all, you should have a clear idea of what happens when a user submits a form that has a JavaScript validation script.
The form is checked by a JavaScript like the one described below. If the script finds a mistake the submission is halted here. The user sees an alert and is asked to re-enter some data.
If nothing is wrong—or if JavaScript is disabled—the form is sent to the server and is processed by a CGI script. If the CGI script finds a mistake it generates some HTML with an error message and sends it back to the user. In this case the user has to go back to the form, re-enter some values and again submit it. If no mistakes are found, the CGI script does whatever it has to do with the data and directs the user to a Thank You page.
As you see, the form is checked for mistakes twice: by the JavaScript and by the CGI script. The CGI check always works, since CGI is server side. The JavaScript check only works when the user has JavaScript enabled. It follows that the CGI check is the most reliable: it always works regardless of what browser is used. Then why use a JavaScript check too? The JavaScript check is very useful in addition to the CGI check because it can catch mistakes before the form is actually sent to the server. Thus the user doesn’t have to use his back button to return to the form, something that may cause confusion, and then search for the incorrect form field, which may cause even more confusion. Therefore the JavaScript check is more user friendly than the CGI check.
In addition, when you use JavaScript the server doesn’t need to spend quite so much time in error handling and is thus a little quicker. This only matters if you have lots and lots of forms, but it’s good to keep it in mind.
So, JavaScript is not a fail-safe method of catching mistakes, but it is very useful as an addition to CGI checks since it lightens the load on the server and is more user friendly.
Therefore I recommend using both JavaScript form checks and CGI form checks. This
way, you get both user friendliness and security.
However, this page contains a more complete overview of how to write a basic form validation script.
On this page I give the code you need for checking user input in a form. Using these bits of code, you can write your own scripts to validate forms
I can’t give you a complete script, because each form and each check are different.
You’ll have to use the elements I explain on this page to build your own script. I created an example form and script that you can study to get the hang of it.
On this page I discuss the limitations of using JavaScript to check a form, then I’ll explain the onsubmit event handler, followed by the few methods and properties of the form itself. Then it’s time for accessing the form elements and the specific syntax for accessing the user defined value of form elements.
Is Your Site Cross-Browser Compatible? — Cross-browser compatible
Compatible with all major browsers available:
I) Internet Explorer
II) Netscape
III) Opera
IV) Firefox
Text based browsers for Lynx operating system or the visually impaired. How does your site look in any of the browsers listed above? Not everyone is using Internet Explorer to surf the Internet these days.
How do I Make My Site Cross-Browser Compatible?
To create a cross-browser compatible web site:
1. Use only standard compliant code
2. Don’t use browser specific (proprietory) HTML tags and features. These only work in the browser they were created for and may even break your page when viewed in another browser.
3. Validate your pages : Validate your HTML/XHTML coding using the W3C free validation service
4. Validate your cascading style sheets using the W3C free validation service.
Some have the “You can’t please everyone” attitude. Yes, your site will look different in each browser because each one interprets the coding differently. The goal with cross-browser compatibility is to make your site viewable in the major browsers available and have the pages render correctly. One thing that will drive visitors away is a site that doesn’t work in their chosen browser.