Closed
Bug 316354
Opened 19 years ago
Closed 18 years ago
Implement type binding restrictions for range
Categories
(Core Graveyard :: XForms, defect)
Core Graveyard
XForms
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: allan, Unassigned)
References
()
Details
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
I think that upload hides itself and puts a message in the JS console.
Reporter | ||
Comment 2•19 years ago
|
||
(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.
Reporter | ||
Comment 3•19 years ago
|
||
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.
Reporter | ||
Updated•18 years ago
|
Assignee: allan → xforms
Comment 4•18 years ago
|
||
I guess the bug is fixed per bug 331984.
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•