Beginning on October 25th, 2016, Persona will no longer be an option for authentication on BMO. For more details see Persona Deprecated.
Last Comment Bug 316354 - Implement type binding restrictions for range
: Implement type binding restrictions for range
Product: Core Graveyard
Classification: Graveyard
Component: XForms (show other bugs)
: Trunk
: All All
: -- normal (vote)
: ---
Assigned To: xforms
: Stephen Pride
Depends on:
Blocks: 322255 326372 326373 334603 343525
  Show dependency treegraph
Reported: 2005-11-14 00:48 PST by Allan Beaufour
Modified: 2016-07-15 14:46 PDT (History)
3 users (show)
See Also:
QA Whiteboard:
Iteration: ---
Points: ---


Description Allan Beaufour 2005-11-14 00:48:03 PST
range should not work for datatypes which it does not support. So we need a "dummy range" to show if range is bound to an invalid datatype. Either a static range which does not do anything, or just a string/image that says "invalid datatype for range".

Related to bug 316353
Comment 1 aaronr 2005-11-14 09:14:00 PST
I think that upload hides itself and puts a message in the JS console.
Comment 2 Allan Beaufour 2005-11-14 09:28:38 PST
(In reply to comment #1)
> I think that upload hides itself and puts a message in the JS console.

No. it is bound to a special "disabled upload" dummy control.
Comment 3 Allan Beaufour 2005-11-16 04:08:49 PST
Argh, this is worse to do than I originally thought. Until now I've ignored XML Schema the best I could... we need a specific binding for each of these built-in datatypes:
* decimal
* float
* double
* integer
* nonPositiveInteger
* negativeInteger
* long
* int
* short
* byte
* nonNegativeInteger
* unsignedLong
* unsignedInt
* unsignedShort
* unsignedByte
* positiveInteger
That's bad. And that still leaves out any user defined types.

I've filed bug 316691 for a better solution to this.
Comment 4 alexander :surkov 2006-09-21 20:52:15 PDT
I guess the bug is fixed per bug 331984.

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