The default bug view has changed. See this FAQ.

Implement type binding restrictions for range

RESOLVED FIXED

Status

Core Graveyard
XForms
RESOLVED FIXED
12 years ago
8 months ago

People

(Reporter: Allan Beaufour, Unassigned)

Tracking

Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

12 years ago
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

12 years ago
I think that upload hides itself and puts a message in the JS console.
(Reporter)

Comment 2

12 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

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

Updated

11 years ago
Blocks: 326372

Updated

11 years ago
Blocks: 326373
(Reporter)

Updated

11 years ago
Assignee: allan → xforms

Updated

11 years ago
Blocks: 343525

Updated

11 years ago
Blocks: 322255

Comment 4

11 years ago
I guess the bug is fixed per bug 331984.
Blocks: 334603
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.