As a security precaution, we have turned on the setting "Require API key authentication for API requests" for everyone. If this has broken something, please contact
Last Comment Bug 316355 - range should consider schema type for begin and end values
: range should consider schema type for begin and end values
Product: Core Graveyard
Classification: Graveyard
Component: XForms (show other bugs)
: Trunk
: All All
: -- normal (vote)
: ---
Assigned To: xforms
: Stephen Pride
Depends on:
Blocks: 326372 326373
  Show dependency treegraph
Reported: 2005-11-14 00:51 PST by Allan Beaufour
Modified: 2016-07-15 14:46 PDT (History)
3 users (show)
See Also:
QA Whiteboard:
Iteration: ---
Points: ---


Description User image Allan Beaufour 2005-11-14 00:51:27 PST
The range control should not only use the begin and end attributes, it should also consider the schema type it is bound to. The spec states that "In the event of overlapping restrictions between the underlying datatype and the start and end hints, the most restrictive range should be used.". So basically "begin" should be max(@begin, schema-lower-limit), and "end" should be min(@end, schema-upper-limit).
Comment 1 User image David Bolter [:davidb] 2016-02-04 12:22:50 PST
RIP xforms

Note You need to log in before you can comment on or make changes to this bug.