[OASIS Issue Tracker] Commented: (OFFICE-1643) Editor Note: Section17.293 form:max-value

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/OFFICE-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11465#action_11465 ] 

Patrick Durusau commented on OFFICE-1643:
-----------------------------------------

But saying that an interface "...will prevent entering values which exceed this limit." is an implementation defined choice of how to deal with invalid values.

The current language: "The form:max-value attribute specifies the maximum value that a user can enter."

Now looks better to me than anything under consideration. Just leave what happens past "the maximum value" undefined. I can imagine an application that simply prevent entry, offers advice on the correct value, marks the control as invalid, disables "save" until corrected, etc. 

I suggest just deleting the editorial note. 

> Editor Note: Section 17.293 form:max-value
> ------------------------------------------
>
>                 Key: OFFICE-1643
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-1643
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>    Affects Versions: ODF 1.2
>            Reporter: Robert Weir 
>            Assignee: Patrick Durusau
>            Priority: Blocker
>             Fix For: ODF 1.2
>
>
> Transcribed from ODF_Revised_Editorial_Notes_27May2009.odt
> Original author: Patrick Durusau
> Section 17.293 form:max-value
> Ed. Note We may want to define how the values are used for valiadation, or maybe even remove them?

-- 
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