<form>
The form element represents a submit-able HTTP request. Unlike HTML, you can not wrap a form element around various input elements within the body. The input element within a form must be of type hidden.
Example
<form id="update" action="http://www.myurl.com/update" method="GET" accept-encoding="GZIP" /> <form id="update" action="http://www.myurl.com/update" method="POST"> <input type="hidden" id="name" value="" /> <input type="hidden" id="pwd" value="" /> <input type="hidden" id="newPwd" value="" /> </form>
Valid Elements
| tag | Valid Occurrences |
|---|---|
| <input> | * |
Element Specific Attributes
| Attribute | Purpose | Values | Default | JIN |
|---|---|---|---|---|
| action REQUIRED |
The action attribute specifies the URL of the request. The path can be relative. | URL | none | 2.0 |
| accept-encoding | The accept-encoding attribute indicates to the server that this device accepts a certain response encoding. Currently the only supported accept-encoding type is "GZIP" and it is supported only on a limited number of devices with native GZIP input streams. | GZIP | none | 2.0 |
| content-encoding | The content-encoding attribute indicates to the server that the content of this request has some form of encoding. Currently the only supported content-encoding type is "GZIP" and it is supported only on a limited number of devices with native GZIP output streams. | GZIP | none | 2.0 |
| method REQUIRED |
The method attribute indicates which HTTP method to submit the request ("GET" or "POST"). There is no default value for the method. | GET, POST | none | 2.0 |
Valid Attributes
idTips and Tricks
The URL of the action can be relative, but its important to note some differences to HTML. A leading / before a relative URL will not refer to the root of a domain. and a relative URL with no symbol in front will attempt to load from the phone's on-board memory. The only valid files that can be accessed this way are the graphics below:
drop_arrow.png
checkbox.png
checkbox_sel.png
default.png
radio.png
radio_sel.png
scroll_down.png
scroll_up.png
where.pngA leading ./ or ../ behave the same as HTML
An example will help illustrate the differences:
URL: http://www.myurl.com/jin/doSomething.jsp
| Action | JIN Resolved URL | HTML Resolved URL |
|---|---|---|
| /showWidget.jsp | http://www.myurl.com/jin/showWidget.jsp | http://www.myurl.com/showWidget.jsp |
| ./showWidget.jsp | http://www.myurl.com/jin/showWidget.jsp | http://www.myurl.com/jin/showWidget.jsp |
| showWidget.jsp | Loads resource from phone | http://www.myurl.com/jin/showWidget.jsp |
| ../showWidget.jsp | http://www.myurl.com/showWidget.jsp | http://www.myurl.com/showWidget.jsp |
For 24/7 support email support@where.com or call 888-262-1150
WHERE™ is a product from uLocate Communications, Inc. ©2007 All Rights Reserved.