Project

General

Profile

Actions

Feature proposal #7620

closed

Improve core field types with HTML5 input types

Added by krileon almost 5 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Target version:
-
Start date:
11 July 2019
Due date:
% Done:

100%

Estimated time:

Description

Integer fields are output as text fields and instead should be output as HTML5 number type. (see #7690)
- https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/number

Implement option for Integer fields to display as range type.

Implement support for decimals in Integer fields (see #7690)
- May require new fieldtype as storage would need to be float instead of int
- Best way to probably do this is if the field as the "Step" parameter configured to allow for a decimal the storage should change to float

Rename Integer fieldtype to Number fieldtype Integer field is already called Integer Number, which is clear enough

Email fields are output as text fields and instead should be output as HTML5 email type.
- https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/email

Date fields (non-dropdown) are output as text fields and instead should be output as HTML5 date type.
- https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/date

Web Address fields are output as text fields and instead should be output as HTML5 url type.
- https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/url

Implement new Color fieldtype
- https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/color

These improvements should also be applied to backend XML driven inputs as well.

Actions #1

Updated by krileon almost 5 years ago

  • Tracker changed from Bug to Feature proposal
Actions #2

Updated by krileon almost 5 years ago

Integer fields also need to support number formatting
- parameter for thousands separator (default: none)
- parameter for decimal separator (default: .)

Actions #3

Updated by beat almost 5 years ago

Actually, that formatting for thousands and decimal separators should be automatically applied when typing in numbers and displaying them, making it as easy as possible for users. It should not be a validation on those details.

We also need to be aware that those two are localization-dependant.

Decimals can be either a dot . or comma ,
Thousands can be a comma (if decimal are dot, like in US), a half-space, an apostrophe ' and even grouping can be by 3 or by 2 digits (India irc).
So we should really let the browser or a well-used JS library handle that imho.

Actions #4

Updated by krileon over 4 years ago

  • % Done changed from 0 to 20
Actions #5

Updated by krileon over 4 years ago

  • % Done changed from 20 to 30

New Decimal Number field implemented and Integer Number changed to HTML5 number input. See #7690

Actions #6

Updated by krileon over 4 years ago

  • Description updated (diff)

Range field makes no sense for nearly all usages. Maybe on some mobile devices it could be useful, but general consensus is a slider field like that is bad UX. If a range fieldtype is implemented it should be 2 side my side number fields to specify an actual range.

Actions #7

Updated by krileon over 4 years ago

  • Description updated (diff)
Actions #8

Updated by krileon over 4 years ago

  • % Done changed from 30 to 50

Email fields changed to email HTML5 email type in #7691

Actions #9

Updated by krileon over 4 years ago

  • Status changed from Assigned to Rejected
  • Target version deleted (CB 2.4.3)
  • % Done changed from 50 to 100

Color fieldtype implement see #7696

Marking ticket rejected as it's a duplicate of individual more specific tickets.

Actions

Also available in: Atom PDF