User tests: Successful: Unsuccessful:
Pull Request for Issue #42579
So far the Integer custom field is a drop-down list.
Though it is crashing the browser when the list becomes too long. Moreover it is really hard to use, after a certain length.
With the PR the Integer custom field is an input of type number. Though, it still follows the min, max and step settings, that existed.
Try setting up a custom field of type "Integer" for an article.
Within the article you will see an input, instead of a drop-down,
Drop-down list.
Input of type number
DKN
Status | New | ⇒ | Pending |
Category | ⇒ | Unit Tests Repository Administration com_admin SQL |
Title |
|
Labels |
Added:
Unit/System Tests
PR-4.4-dev
|
Category | Unit Tests Repository Administration com_admin SQL | ⇒ | Libraries Front End Plugins |
Labels |
Added:
PR-5.2-dev
Removed: Unit/System Tests |
Labels |
Added:
Feature
Removed: PR-4.4-dev |
Title |
|
I have tested this item ✅ successfully on a8e9be4
This does what it says. But Fedik's suggestion below sounds logical to me.
I have tested this item ✅ successfully on a8e9be4
Works like described.
This breaks backwards compatibility and should be a new field
Not setting RTC due to reason stated in previous comment. The "Updates requested" label is already set.
This pull request has been automatically rebased to 5.3-dev.
Title |
|
Thanks for the PR.
Before you continue. We should not change existing integer field. And instead of it, need to create a new Number custom field, which will use NumberField class.