create native HTML5 fields

[icebob]

Because currently there is no vanilla datetime picker. Pickaday is only date selector.

• create new field common type which has a "inputType" property. (break changes)
• rename datetime field to datetimePicker (break changes)
• rename slider field to rangeSlider (break changes)
• update docs (add new radio values description)

Available types

• date
• datetime
• datetime-local
• time
• month
• week

Other HTML5 types

• url
• tel
• radio

Set this inputType to the field type attributes:

input( :type="schema.inputType")

[lionel-bijaoui]

Same thing should be done with slider field. It should be renamed "ion.rangeSlider" or "rangeSlider".
Also a "radio" field ! Switch is cool, but sometime you need more the 2 values.
And "tel" for a native masked/cleave for phone number only.
Last one is "url".
I would also like to point out that we need more HTML5 attributes:

• autofocus
• inputmode
• selectionDirection
• spellcheck

specific to text, search, tel, url or email:

• pattern
• size (also for password)

💥 More HTML5! 💥

[icebob]

HTML5 range is exist as fieldRange. I added the other types to the tasklist.

what is the size attr?

[lionel-bijaoui]

Yeah, sorry I forgot to remove that sentence.

size
The initial size of the control. This value is in pixels unless the value of the type attribute is text or password, in which case, it is an integer number of characters. Starting in HTML5, this attribute applies only when the type attribute is set to text, search, tel, url, email, or password; otherwise it is ignored. In addition, the size must be greater than zero. If you don't specify a size, a default value of 20 is used. HTML5 simply states "the user agent should ensure that at least that many characters are visible", but different characters can have different widths in certains fonts; in some browsers, a certain string with x characters will not be entirely visible even if size is defined to at least x.

Source

I think the goal for v1.0.0 is to have all attributes exposed for native HTML5 fields.

[icebob]

I think, the size is not neccessary, because the default width is 100%. So it is overwrite the size attr.
And you can change the width via styleClasses property in schema

[lionel-bijaoui]

Yes, but if you change the width via styleClasses and then, you may want to use it for some reason. I mean, it don't cost much to add, why not add it just in case someone needs it ?

[lionel-bijaoui]

@icebob We need a radio field, right ?