Forms

Forms, when well designed, work well on our receivers. Problems reported in the past generally fall into one of a few categories.

Forms Processors We do not support Java or VBS. If you try to run an application, such as a shopping cart or registration that requires the client browser to perform some task in these languages, it may appear that your form is causing an error. Make sure you are using a forms processor that does not rely on client side Java or other unsupported languages.

Sloppy Code Our receivers can be more stringent in the interpretation of HTML than other browsers. Errors that may slide through processing in those applications may get caught in the TV browser and cause an error. Always check the code first for syntax, spelling, and consistency. It may be helpful to use one of the many HTML validators available on the Web.

JavaScript Conflicts While we strive to support the full implementation of JavaScript 1.3, some of the elements are simply not going to work as expected. For details, please refer to the JavaScript resource on this site.

Editors Sometimes a WYSIWYG HTML editor, like Microsoft® FrontPage®, can add information within the form that is not standard. The following example code illustrates one form that was generated using FrontPage that was reported to not work correctly:
<form method="POST" <!--webbot bot="SaveResults" startspan u-file="_formdata/subscriber.txt" s-format="TEXT/TSV" s-label-fields="TRUE" b-reverse-chronology="FALSE" s-e-mail-format="TEXT/PRE" s-e-mail-address="live@nowhere.com" b-e-mail-label-fields="FALSE" b-e-mail-replyto-from-field="TRUE" s-e-mail-replyto="Reply to" b-e-mail-subject-from-field="FALSE" s-e-mail-subject="HCTR Subscription" s-builtin-fields="Date Time REMOTE_NAME REMOTE_USER HTTP_USER_AGENT" action="_vti_bin/shtml.exe/subscribe.htm" onsubmit="return FrontPage_Form2_Validator(this)" name="FrontPage_Form2" webbot-action="--WEBBOT-SELF--">

Removing everything before the action attribute (set in bold for emphasis only) resolved the error. (An HTML validator did report an error in this tag). Always check for extraneous information within the <FORM> tag itself if a problem persists.

Forms Processors	We do not support Java or VBS. If you try to run an application, such as a shopping cart or registration that requires the client browser to perform some task in these languages, it may appear that your form is causing an error. Make sure you are using a forms processor that does not rely on client side Java or other unsupported languages.
Sloppy Code	Our receivers can be more stringent in the interpretation of HTML than other browsers. Errors that may slide through processing in those applications may get caught in the TV browser and cause an error. Always check the code first for syntax, spelling, and consistency. It may be helpful to use one of the many HTML validators available on the Web.
JavaScript Conflicts	While we strive to support the full implementation of JavaScript 1.3, some of the elements are simply not going to work as expected. For details, please refer to the JavaScript resource on this site.
Editors	Sometimes a WYSIWYG HTML editor, like Microsoft® FrontPage®, can add information within the form that is not standard. The following example code illustrates one form that was generated using FrontPage that was reported to not work correctly: <form method="POST" <!--webbot bot="SaveResults" startspan u-file="_formdata/subscriber.txt" s-format="TEXT/TSV" s-label-fields="TRUE" b-reverse-chronology="FALSE" s-e-mail-format="TEXT/PRE" s-e-mail-address="live@nowhere.com" b-e-mail-label-fields="FALSE" b-e-mail-replyto-from-field="TRUE" s-e-mail-replyto="Reply to" b-e-mail-subject-from-field="FALSE" s-e-mail-subject="HCTR Subscription" s-builtin-fields="Date Time REMOTE_NAME REMOTE_USER HTTP_USER_AGENT" action="_vti_bin/shtml.exe/subscribe.htm" onsubmit="return FrontPage_Form2_Validator(this)" name="FrontPage_Form2" webbot-action="--WEBBOT-SELF--"> Removing everything before the action attribute (set in bold for emphasis only) resolved the error. (An HTML validator did report an error in this tag). Always check for extraneous information within the <FORM> tag itself if a problem persists.