[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (OFFICE-2925) 19.315 form:validation - scope of validation - see description
[ http://tools.oasis-open.org/issues/browse/OFFICE-2925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Weir updated OFFICE-2925:
---------------------------------
Summary: 19.315 form:validation - scope of validation - see description (was: 19.317 form:validation - scope of validation - see description)
Description:
This may not be fixable for this release, but...
form:validation only provides validation for data entry by <form:formatted-text>
That is to say that validation is not provided for <form:number>, <form:date>, <form:time>, <form:value-range>.
Note that form:max-value sets an upper bound for <form:number>, <form:date>, <form:time>, <form:value-range> and, of course, <form:formatted-text>.
Note that form:min-value sets an upper bound for <form:number>, <form:date>, <form:time>, <form:value-range> and, of course, <form:formatted-text>.
So, validation, at least in the sense of 19.315 is something different from setting upper and lower boundaries.
Problem: There is no validation for <form:number>, <form:date>, <form:time>, <form:value-range>.
Problem: Don't define what happens if min/max values are exceeded.
As I said, this may not be fixable now but we need to be aware of it.
was:
This may not be fixable for this release, but...
form:validation only provides validation for data entry by <form:formatted-text>
That is to say that validation is not provided for <form:number>, <form:date>, <form:time>, <form:value-range>.
Note that form:max-value sets an upper bound for <form:number>, <form:date>, <form:time>, <form:value-range> and, of course, <form:formatted-text>.
Note that form:min-value sets an upper bound for <form:number>, <form:date>, <form:time>, <form:value-range> and, of course, <form:formatted-text>.
So, validation, at least in the sense of 19.317 is something different from setting upper and lower boundaries.
Problem: There is no validation for <form:number>, <form:date>, <form:time>, <form:value-range>.
Problem: Don't define what happens if min/max values are exceeded.
As I said, this may not be fixable now but we need to be aware of it.
> 19.315 form:validation - scope of validation - see description
> --------------------------------------------------------------
>
> Key: OFFICE-2925
> URL: http://tools.oasis-open.org/issues/browse/OFFICE-2925
> Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
> Issue Type: Bug
> Components: Forms
> Affects Versions: ODF 1.2 CD 05
> Reporter: Patrick Durusau
> Assignee: Patrick Durusau
> Fix For: ODF-Next
>
>
> This may not be fixable for this release, but...
> form:validation only provides validation for data entry by <form:formatted-text>
> That is to say that validation is not provided for <form:number>, <form:date>, <form:time>, <form:value-range>.
> Note that form:max-value sets an upper bound for <form:number>, <form:date>, <form:time>, <form:value-range> and, of course, <form:formatted-text>.
> Note that form:min-value sets an upper bound for <form:number>, <form:date>, <form:time>, <form:value-range> and, of course, <form:formatted-text>.
> So, validation, at least in the sense of 19.315 is something different from setting upper and lower boundaries.
> Problem: There is no validation for <form:number>, <form:date>, <form:time>, <form:value-range>.
> Problem: Don't define what happens if min/max values are exceeded.
> As I said, this may not be fixable now but we need to be aware of it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]