W3C Validation on textarea form element

Whats the proper way to construct a textarea tag?
here's my tag:
<textarea name="message" id="message"></textarea>
css to style it:
#contactform textarea {
margin-bottom:8px;
width:350px;
height:200px;
When i run the page through the validator it gives me 2
errors:
required attribute "rows" not specified
required attribute "cols" not specified
Whats the proper way to avoid these errors when specifying
width and height with CSS?
Thanks,
Jeremy

Jeremy,
Like so:
<textarea name="message" rows="20" cols="80"
id="message"></textarea>
Ken Ford
Adobe Community Expert
"bigj9901" <[email protected]> wrote in
message
news:e7u449$8v1$[email protected]..
> Whats the proper way to construct a textarea tag?
>
> here's my tag:
> <textarea name="message"
id="message"></textarea>
>
> css to style it:
> #contactform textarea {
> margin-bottom:8px;
> width:350px;
> height:200px;
> }
>
> When i run the page through the validator it gives me 2
errors:
>
> required attribute "rows" not specified
> required attribute "cols" not specified
>
> Whats the proper way to avoid these errors when
specifying width and
> height
> with CSS?
>
> Thanks,
> Jeremy
>
>
>

Similar Messages

HTML5 Form Element Validation

Hi Eloqua people
Has anyone worked out a way of using Live Validation on HTML5 form elements, such as url, tel, or email? I'm trying to avoid having to go and look for a new validation script and to apply it manually.
Thanks,
Sam

I want to have control over certain 'dimension type of' columns in the classic report / tabular form with APEX_ITEM.* in the sql for the report while some of the columns are from Collection with their collection column names. C001, C002 etc..
...clips
SELECT
APEX_ITEM.SELECT_LIST_FROM_LOV(35
,C035,'LOV_ANIMALS'
,'style="width:50px"','YES',NULL,NULL
,'f35_' || LPAD (seq_id, 4, '0'),NULL) animals
,to_number(c001) c001
,to_number(c002) c002
FROM apex_collections WHERE collection_name = 'SLEEPY_ANIMAL'
...clips
When there are several columns in the report, it is easier to maintain C001...columns appearance in the Report Attributes-->Column Attributes.
Oh yes, I have adapted Denes dynamic cascading lov for tabular forms which is the reason for having the "APEX_ITEM..." in the query and from some blog I read that it is very good to toss those 'dimension' type of columns to high-end numbers in the collection, so there will be space for the entry columns.
E.g. firstrow in the tabular form
c035 -- animals --> f35 --> f35_0001 (select list with lov LOV_ANIMALS)
c001 -- "what ever I have said in Column attributes"--> f01 --> f01_0001 (text area, editable column)
c002 -- "what ever I have said in Column attributes"--> f02 --> f02_0001 (text area, editable column)
So the numbering is the same for the www-form and collection columns.
Everything is ok if the columns c001 and c002 are editable e.g. 'text area' type, but if I change c001 to 'Display..' type then the order for item_id's change.
c035 -- animals --> f35 --> f35_0001
c001 -- "what ever I have said in Column attributes" (display as text (escape special chars...))
c002 -- "what ever I have said in Column attributes"--> f01 --> f01_0001
So now the collection column c002 accidentally is mapped to forms f01-column while I might assume it is f02.
rgrds Paavo

Validating date form element

Operating system and version: Win 2000
Macromedia product and version: DW8
Browser and version: IE7
Steps to reproduce:
1) Add a form
2) Name a text form element named: <%= (iCount &
".Qty") %>
3) Add a button
4) Add a date validation, or better said .. try to.
The form element is not listed in the form, form elements
NEEDS to be named
as above (<%= (iCount & ".Qty") %>)
I even tried renaming the element to say 'date', it worked, I
apply the
validation and then on the code replace 'date' for '<%=
(iCount & ".Qty")
%>', but it doesnt work.
I am using ASP/VB with MS SQL 2000
How should I solve this ? I cannot change the name of the
element and need
to validate that the element is a date (mm/dd/yyyy).
Bottom line: While the element is named <%= (iCount &
".Qty") %> I
cannot apply a validation to it, tried several extensions,
none work.
Please advice,
Alejandro

I want to have control over certain 'dimension type of' columns in the classic report / tabular form with APEX_ITEM.* in the sql for the report while some of the columns are from Collection with their collection column names. C001, C002 etc..
...clips
SELECT
APEX_ITEM.SELECT_LIST_FROM_LOV(35
,C035,'LOV_ANIMALS'
,'style="width:50px"','YES',NULL,NULL
,'f35_' || LPAD (seq_id, 4, '0'),NULL) animals
,to_number(c001) c001
,to_number(c002) c002
FROM apex_collections WHERE collection_name = 'SLEEPY_ANIMAL'
...clips
When there are several columns in the report, it is easier to maintain C001...columns appearance in the Report Attributes-->Column Attributes.
Oh yes, I have adapted Denes dynamic cascading lov for tabular forms which is the reason for having the "APEX_ITEM..." in the query and from some blog I read that it is very good to toss those 'dimension' type of columns to high-end numbers in the collection, so there will be space for the entry columns.
E.g. firstrow in the tabular form
c035 -- animals --> f35 --> f35_0001 (select list with lov LOV_ANIMALS)
c001 -- "what ever I have said in Column attributes"--> f01 --> f01_0001 (text area, editable column)
c002 -- "what ever I have said in Column attributes"--> f02 --> f02_0001 (text area, editable column)
So the numbering is the same for the www-form and collection columns.
Everything is ok if the columns c001 and c002 are editable e.g. 'text area' type, but if I change c001 to 'Display..' type then the order for item_id's change.
c035 -- animals --> f35 --> f35_0001
c001 -- "what ever I have said in Column attributes" (display as text (escape special chars...))
c002 -- "what ever I have said in Column attributes"--> f01 --> f01_0001
So now the collection column c002 accidentally is mapped to forms f01-column while I might assume it is f02.
rgrds Paavo

h:form with W3C validation failure

Hi gurus,
I tried to validate my JSF page against W3C validation rules. However, each <h:form> in my page creates a hidden field as:
"+<input type="hidden" name="javax.faces.ViewState" id="javax.faces.ViewState" value="j_id14:j_id15" />+"
with same id and value, so as a result, i can't pass the validation.
So could anyone has a suggestion on this problem?
BTW, i found some threads suggest to use a "giant" h:form for the entire page, and clearly this is not the answer i am looking for.
Thanks in advance!

Yep, it's a known issue.
I've attempted fixes in the RI in the past, however due to potential reliance on the presence of both
fields for AJAX libraries+JSF, it's left as is.

Firefox 4 on Windows 7/XP is not allowing user interaction with form elements that contain HTML coding. For instance, a textarea element whose content includes h4 My Content /h4 br /

On a Mac, Firefox 4 was also dysfunctional and the "enter" key immediately submitted the form instead of adding a line if the cursor was placed inside content to start with, but on Windows it seems impossible to get the cursor inside the textarea content at all.
The "view source" of the form textarea element plus the content that our user entered is pasted below:
<textarea name="content" cols="120" rows="50"><h4>SEARCH TOOL NOT WORKING</h4><br>
<h3>TRY FIRST</h3>
<P>Check for popup blockers; set for allow<br>
Mac users may want to use Firefox if Safari does not work and not a popup problem.</P>
<h3>COMMUNICATION FOR TROUBLESHOOTING </h3>
<p>Must provide the following information:<br>
Computer's operating system?<br>
Browser and version?<br>
On campus or off, if off how are you getting a Brown IP address?<br>
What in detail is wrong?<br>
What have you tried to overcome the problem?
</p>
<h3>IF ALL ELSE FAILS</h3>
<p>Contact CIS HELP - it may be your computer.
<p>A computer cluster in one of the libraries or CIT if the problem is not with the vendor. </p></textarea>

p.s. I realize that the user content is somewhat confusing, and your web page interprets the HTML tags instead of displaying them explicitly...
The user content begins after the <textarea> element and includes HTML headers, breaks, etc. Other HTML content inside form elements gave similar results. Thanks!

Missing Validation Form Elements

OK, perhaps this is just an oversight.
bullet]Is there an issue with Radio buttons?[
Also, what about the password form
element? We can set length and some other params on that also but
that is missing, right?
Was that just an oversight in this
release? (And if yes, could it be done added to a 1.4.1
release?

Radio buttons have a couple of validation points. One point
is that they may have no default value and one needs to be set to
submit the form. The other is it may have a default value set like
(none selected) but that isn't valid and it can be anyone other
than that. Personally I don't agree with some of the form fields
"required" by those whom we work for, yet these things still
apperar on forms and if this solution doesn't cover those
situations then those who don't understand will determine the issue
is SPRY, and we don't want that. :)
I think in passwords (which are "like" text input elements,
but are not text input elements) we will still need to handle the
length and possible the "complexity" settings for when people enter
in original passwords. I have seen this done before and it is very
well recieved by those who are asking for web applications to be
built.
Does that make sense? BTW... the logic I have done in the
past says that the validation routines for radio buttons is very
simular to the logic for select boxes.
That does bring one more thought to mind... what about select
boxes that are multi-select? Do we have that covered?

Dreamweaver 2004 MX is not recognizing my form elements

Has anyone run into a problem with an insert or update server
behavior not recognizing form elements? I created the page and now
when I try to make any changes I get an error.
"Column 'sccb_comments' is mapped to a form element that does
not exist. Please map the column to an existing form element or set
its value to 'None'."
The problem is that the insert dialog box recognizes the
form, but not any of the elements in it.
I know that I need to upgrade to CS4, tell my director to
cough up the funds.

There must be something else happening on your page. But I
have no idea
what that might be. This should work. Sorry.
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"Reidster" <[email protected]> wrote in
message
news:[email protected]...
> Murray,
>
> You replied,
> "It wouldn't matter. It's perfectly valid to have
<div> tags in side
> <form>
> tags. And it's not DW's preferences you need to worry
about - it's HTML's
> preferences, so to speak. I suspect that something else
entirely is
> causing the
> problem. Without seeing your code, though, we cannot
know what that might
> be."
>
> Sometimes what should work or one would think should
work doesn't. As in
> my
> case, the <div> tags inside my for was the issue.
Here is the original
> code
> that did not allow me to assign form objects to fields
in my database. The
> server behavior also displayed an '!' in the application
window until I
> moved
> the <div> tags outside of my form.
>
> <form name="frmEditRelease" id="frmEditRelease"
method="POST"
> action="<?php
> echo $editFormAction; ?>">
> <div id="new_prod_rel">
> <p><select name="sccb_status"
id="sccb_status">
> <option value="0" <?php if (!(strcmp(0,
> $row_rsEditRelease['sccb_status']))) {echo "SELECTED";}
?>>Open</option>
> <option value="1" <?php if (!(strcmp(1,
> $row_rsEditRelease['sccb_status']))) {echo "SELECTED";}
> ?>>Pending</option>
> <option value="2" <?php if (!(strcmp(2,
> $row_rsEditRelease['sccb_status']))) {echo "SELECTED";}
> ?>>Approved</option>
> <option value="3" <?php if (!(strcmp(3,
> $row_rsEditRelease['sccb_status']))) {echo "SELECTED";}
?>>Denied</option>
> <option value="4" <?php if (!(strcmp(4,
> $row_rsEditRelease['sccb_status']))) {echo "SELECTED";}
> ?>>Deleted</option>
> <option value="5" <?php if (!(strcmp(5,
> $row_rsEditRelease['sccb_status']))) {echo "SELECTED";}
> ?>>Deferred</option>
> </select>
> <label for="sccb_status">SCCB Status</label>
> </p>
> <p>
> <select name="sRelease">
> <?php do { ?>
> <option value="<?php echo
$row_rsProj['project_vchar']?>"
> <?php
> if (!(strcmp($row_rsProj['project_vchar'],
> $row_rsEditRelease['release'])))
> {echo "SELECTED";} ?>><?php echo
$row_rsProj['project_vchar']?></option>
> <?php } while ($row_rsProj =
mssql_fetch_assoc($rsProj));
> $rows = mssql_num_rows($rsProj);
> if($rows > 0) {
> mssql_data_seek($rsProj, 0);
> $row_rsProj = mssql_fetch_assoc($rsProj);
> }
> ?>
> </select><label for="sRelease">
Release</label>
> </p>
> <p>
> <select name="lifecycle">
> <option value="System Reqts." selected="selected"
<?php if
> (!(strcmp("System Reqts.",
$row_rsEditRelease['lifecycle']))) {echo
> "SELECTED";} ?>>System Reqts.
> <option value="Analysis" <?php if
(!(strcmp("Analysis",
> $row_rsEditRelease['lifecycle']))) {echo "SELECTED";}
?>>Analysis
> <option value="Design" <?php if
(!(strcmp("Design",
> $row_rsEditRelease['lifecycle']))) {echo "SELECTED";}
?>>Design
> <option value="Code" <?php if (!(strcmp("Code",
> $row_rsEditRelease['lifecycle']))) {echo "SELECTED";}
?>>Code
> <option value="Testing Phase 1" <?php if
(!(strcmp("Testing Phase
> 1",
> $row_rsEditRelease['lifecycle']))) {echo "SELECTED";}
?>>Testing Phase 1
> <option value="Testing Phase 2" <?php if
(!(strcmp("Testing Phase
> 2",
> $row_rsEditRelease['lifecycle']))) {echo "SELECTED";}
?>>Testing Phase 2
> <option value="Alpha" <?php if (!(strcmp("Alpha",
> $row_rsEditRelease['lifecycle']))) {echo "SELECTED";}
?>>Alpha
> <option value="Beta" <?php if (!(strcmp("Beta",
> $row_rsEditRelease['lifecycle']))) {echo "SELECTED";}
?>>Beta
> <option value="Gen. Release" <?php if
(!(strcmp("Gen. Release",
> $row_rsEditRelease['lifecycle']))) {echo "SELECTED";}
?>>Gen. Release
> </select><label for="lifecyle">
Lifecycle</label>
> <input name="sub_ticket_id" type="hidden"
id="sub_ticket_id"
> value="<?php echo
$row_rsEditRelease['sub_ticket_id']; ?>">
> </p>
> <p>
> <input <?php if
(!(strcmp($row_rsEditRelease['test_only'],1)))
> {echo
> "checked";} ?> name="test_only" type="checkbox"
id="test_only" value="1">
> <label for="test_only">
Test Only
> <input name="ticket" type="hidden" id="ticket"
value="<?php echo
> $row_rsEditRelease['Ticket']; ?>" />
> </label>
> </p>
> <p><label for="sccb_comments">SCCB
Comments</label><br /><textarea
> name="sccb_comments" cols="60" rows="5"><?php echo
> $row_rsEditRelease['sccb_comments'];
?></textarea>
> </p>
> <p>
> <input type="submit" name="Submit" value="Submit"
/>
> </p>
> </div>
> <input type="hidden" name="MM_update"
value="frmEditRelease">
> </form>
>
> It's not until if move the <div> tags outside of
the <form> tags does the
> '!'
> on the update server behavior go away.
>
> Any thoughts?
>

Passing Session Values to the Tabular Form Element of a Report Column

Hello,
I'm running application express version 2.0 with a 10.2.0.2.0 database on a 32 bit windows box. I'm trying to figure out sneaky a way to pass the &APP_PAGE_ID., #APP_PAGE_ID# or V('APP_PAGE_ID'); as an element attribute of a Report Tabular Form Element set to display as a Select List (named LOV).
It seems that whatever option I choose, the Element Attributes field will only render the literal value of what I have entered. This is part of the solution but I would like to find a way to pass the current page id.
What I'm trying to do is utilize the ONCHANGE attribute to redirect to a report page in my application when the value from a Select List (named LOV) is selected.
I could work around this by creating my own table output with PL/SQL and HTP.P commands but would really be interested in finding out if I can use the reporting structures which are already available through Application Express.
Any ideas?
Thanks.
Justin.

Thanks for the response Earl. To clarify this is what I've done and what I hope to achieve:
I currently have a LOV for my application that identifies a number of database report types: DB Options, DB Parameters, DB Version, and so on.
I have an application express report being generated for the databases I'm monitoring and it displays as follows:
- HOST -- DBTYPE -------- DBNAME - DBREPORTS
=====================================
- SVR 1 - Oracle 9.2.0.1 - DEV -------- [LOV HERE]
- SVR 2 - Oracle 9.2.0.7 - TST --------- [LOV HERE]
I am displaying the LOV on my report the the options under the reports attribute tab in my application builder. I insert my LOV select list by editing the DBREPORTS column and set the "Display As:" option under Tabular Form Element to "Select List (named LOV)"; I have also added my LOV to the "Named LOV" option under List of Values.
So far this achieves everything I would expect and works quite well (a select list with my report types appears in my monitor report for each DB that is returned).
What I'm interested in doing now is opening a DBREPORT for a given database by simply choosing the report type from my LOV. I can set the "Element Attributes" option under Tabular Form Element to execute a javascript call for any valid event (in my case I'm using ONCHANGE).
My only issue is that I cannot find a way to pass any session values from my page to my Element Attribute. If, in the Element Attributes field I enter:
onchange="alert(this.value);" //my dialogue box will display the value of my current selection when I choose a report type.
What I'd love to be able to do is something like:
onchange="alert('&APP_PAGE_ID.');" //so my current page id is written to the element.
Unfortunately, only my literal text seems to be rendered. Rather than having my dialogue come back with my page number, say 75, I receive the literal value &APP_PAGE_ID.
Notwithstanding any quote issues, I've tried to dump a test html attribute to my source html by entering any of the following in the Element Attributes field:
test=&APP_PAGE_ID.
test=#APP_PAGE_ID#
and as a shot in the dark knowing that I'm not using PL/SQL:
test=V('APP_PAGE_ID');
In every case when I view source I see the literal value of what was entered in the Element Attributes field (ie "test=&APP_PAGE_ID." instead of "test=75").
What makes things a little more frustrating is that I can drop &APP_PAGE_ID. into the Column Heading field (ex My Heading &APP_PAGE_ID.), it renders as I would expect; "My Heading 75". If we could find a solution to this, I could see a number of slick uses for this type of functionality.
Hope this helps,
Thanks.
Justin.

How to track changes made in a jsf form element.

I am in a page and editing some form elements. I click on some other link which will take me to another page. Before moving to another page I want to check if there are some unsaved data in the page. If some form elements are edited, I want to throw a confirmation alert, if the user wants to move to the other page without saving the edited data.
This can be accomplished by having a hidden flag which will keep a track. On change of any element, a javascript function will be called to set the hidden flag. So before going to any page we can check the flag and throw an alert.
But this process will be needing much coding effort. Is there a way in JSF to track the change in a form by backing bean or some other process?

JSF offers a serverside ValueChangeEvent for that. Every UIInput component supports a 'valueChangeListener' attribute (and a f:valueChangeListener facet) which can point to a method in the backing bean which takes a ValueChangeEvent parameter. This will only be invoked if the new value differs from the old value. This costs one trip to the server though.
E.g.<h:inputText value="#{myBean.value}" valueChangeEvent="#{myBean.valueChanged}" />MyBeanpublic void valueChanged(ValueChangeEvent event) {
    Object oldValue = event.getOldValue();
    Object newValue = event.getNewValue();
    // Do your thing.
}ValueChangeEvents are invoked in the 3rd phase of the JSF lifecycle, after validation/conversion and before update model values. Also see http://balusc.blogspot.com/2006/09/debug-jsf-lifecycle.html

Menu problem with w3c validator

DW CS5.5
When I test a php page with a select menu in the w3c validator, I get the following error message on each element within it:
The select element cannot have more than one selected option descendant unless the multiple attribute is specified. [HTML5]
Whether selected as a menu or a list, it still appears. I was under the impression that you only select one item from a list unless you check "allow multiple" and I only need one item to be selected.
The list or menu displays and works properly, selecting one item as required.
Is this a validator error or is there something wrong with my DW generated code? - shown as a list in this case:

Most containers have their own XML parsing JAR's. You do not want to normally remove these (as they parse XML deployment and configuration files). However, you can add your own XML parsing JAR files to WEB-INF/lib.
- Saish

Removal of af:form element

Hi all,
JDeveloper 11.1.1.6.0
We're in the process of implementing a credit card processing page that will be performing a cross domain form action via jQuery or some other means. One of our primary requirements is to guarantee that form data on this page is not submitted to our server but we would like ADF to render the page to maintain a consistent look and feel for the site.
Would dropping the af:form element be an effective means of guaranteeing form data is not sent to our WLS server (via post, ajax, server side validation)? Any pitfalls?
Thanks!

Hi,
removing the af:form element will not generate the HTML form element and this not submit anything to the server. So yes, this would work.
Frank

Accessing parent window form elements from a JSP file

Actually I have a JSP page . It calls a popup function to load another JSP file on the event Onclick of a label. In the JSP file loaded on the popup window, I need to access the form elements of the parent.
Eg: the Parent has a Textarea named "ta_1" in the form "appl_1".
Now i cannot access this element in the child JSP page using,
window.opener.document.ta_1.appl_1.value;
The window.opener is not defined for this HTML page cos the HTML page was generated as an output of the JSP file.
Please give a JSP code snippet which accesses the parent form element..

Actually I have a JSP page . It calls a popup function to load another JSP file on the event Onclick of a label. In the JSP file loaded on the popup window, I need to access the form elements of the parent.
Eg: the Parent has a Textarea named "ta_1" in the form "appl_1".
Now i cannot access this element in the child JSP page using,
window.opener.document.ta_1.appl_1.value;
The window.opener is not defined for this HTML page cos the HTML page was generated as an output of the JSP file.
Please give a JSP code snippet which accesses the parent form element..

Creating form element from within a component

Hi all,
I am trying to create a form element within a component
function which is then called from a .cfm page which has the cfform
tags. I keep getting a context validation error for the form
element tag. Here is some sample code:
<cfcomponent name="yourComponent">
<cffunction name="createTag" returntype="string"
access="public">
<cfsavecontent variable="returnContent">
<cfselect name="thisSelect">
<option value="0">Value 1</option>
</cfselect>
</cfsaveconten>
<cfreturn returnContent>
</cffunction>
</cfcomponent>
And in the .cfm page:
<cfform>
<cfinvoke component="yourComponent" method="createTag"
returnVariable="returnContent"/>
<cfoutput>#returnContent#</cfoutput>
</cfform>
The error occurs in the function and it says the cfselect
must be within a cfform. I tried the function without the save
content and just set the output="yes" but the same error occurs.
Any help appreciated in how to get around this. Just putting
the code in the .cfm is not an option for this.
Any help appreciated.
Jim

quote:
Originally posted by:
jim1234
Thanks for the reply. Yes, that works. So it looks like it
has to do with the function call.
After some further investigation, I found out that a regular
<select> works, it's just the <cfselect> that does not.
ColdFusion wants it directly within the <cfform> tag.
Something does not make sense. If the cfsavecontent worked in
the cfm file, there is no reason for it not to work in a cfc.
If you want to persue this, the next troubleshooting step is
to copy the function to your cfm file and see if it works. I
suspect that you are trying something simple as a proof of concept.

Show / Hide form elements

Hi...
I just want to know, how I can create the following in
Dreamweaver CS3:
Eg: I have 4 form elements: Active, Name, Surname, Comments
Now. When viewing the page containing the form, it should
only display the Active Tickbox. WHEN you have ticked the Active
tickbox, it should then UNHIDE the Name, Surname and Comments
elements.
Any Ideas how it could be done using Dreamweaver...? Even if
it can be done like except hiding elements, just make the other
elements "locked" or grayed out...?
Thanx...

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
Transitional//EN"
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="
http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8" />
<title>Untitled Document</title>
<meta http-equiv="imagetoolbar" content="no" />
<meta name="MSSmartTagsPreventParsing" content="TRUE"
/>
<meta name="robots" content="index,follow" />
<script type="text/javascript">

</script>
<style type="text/css">
#foo { display:none; }
</style>
</head>
<body>
<form id="form1" name="form1" method="post" action="">
<p>
<label for="checkme">Want more?</label>
<input name="checkme" type="checkbox" id="checkme"
onclick="MM_changeProp('foo','','display','block','DIV')"
/>
</p>
<div id="foo"><p>
<label for="field1">Thing One</label>
<input type="text" name="field1" id="field1" />
</p>
<p>
<label for="field2">Thing Two</label>
<input type="text" name="field2" id="field2" />
</p></div>
</form>
</body>
</html>
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"RadeonX" <[email protected]> wrote in
message
news:ge8tl2$oi8$[email protected]..
> OK... Is there maybe a step-by-step instruction or an
Example which I can
> use to help me, as I am rather new with this kind of
stuff...? Thanx...

Spry Elements vs Regular Form Elements

What is the difference between using Spry Validation form elements as opposed to just using regular form elements?
Which do you prefer and why?
Thanks

What is the difference between using Spry Validation form elements as opposed to just using regular form elements?
Regular form elements are passive elements that wait for information to be entered to subsequently be processed by another mechanism.
SpryValidation form elements are the same as above except that they have an active validation module attached. There are standard validation rules that can be used (like e-mail address) or you can supply custom validations.
Because Spry is a JavaScript library, the Spry widgets will only work with JavaScript enabled. The advantage of JavaScript is that it is processed by the browser (client side) and that, in our case, validation is instantaneous. When JS is turned off or the browser is not JS capable, there is no validation. This means that if you require serious validation, you must, in addition/in lieu of, have server side validation.
Which do you prefer and why?
I use both client side (Spry) and server side (PHP) validation, the latter to make sure that if Spry fails there is always the safe and trusted method of validation.
Why Spry? Spry widgets allow for a better user experience.
I hope this helps.
Ben

W3C Validation on textarea form element

Similar Messages

Maybe you are looking for