|
Attribute |
Value |
|---|---|
| Physical Property Name | ClientSyntaxCheck |
| Property Type | uboolean |
| Dynamic? | No |
| Default value |
CommandButton, FlatButton, PictureButton, Picture, Label, StaticText, and RawHtml. |
|
Value |
Description |
|---|---|
|
|
Prevents the browser from sending a request if a field value is syntactically incorrect. |
|
|
Allows the browser to send the request, even if the content of a field is syntactically incorrect. |
Description
By default, when the value of a DSP field is changed, the syntax is checked in the client, and if it has a value that is incorrect according to its syntax definition, the browser does not send any request to the server.
Setting the Syntax
Check on the Browser (ClientSyntaxCheck) to false, overrides this behavior and allows the data to be submitted to the server, regardless of its validity.
Note: This does not disable the syntax check; it just makes it possible for the browser to submit a request, even if a field holds syntactically incorrect data.
When the data is submitted, it is not validated by webload. If it contains errors, these are detected only when the data is validated, either by an explicit validate statement or implicitly if the data is stored. In this case, the response will include validation errors. Depending on your use case, you need to take this behavior into account.
There are valid situations for allowing data to be submitted. For example, button widgets contain no data that needs validating, so clientsyntaxcheck is explicitly set to false in the initialization file.
You may have your own use cases where submitting syntactically invalid data is not a concern—you may want to validate it on the server, or you do not need to store the data, or you have customized behavior to ensure it is valid. Whatever the case, if you set this property to false, you are responsible for how invalid data is handled and will need to ensure its integrity.
