[#24122] - [4.0] Add fancy select layout to multiple select lists
- Closed
- 16 Apr 2019
- Medium
- Build: 4.0-dev
- # 24122
- Diff
- bembelimen:multiple-list-fancy-select
- Success continuous-integration/travis-ci/pr The Travis CI build passed Details
- Success continuous-integration/appveyor/pr AppVeyor build succeeded Details
- Success continuous-integration/drone/pr the build was successful Details
User tests: Successful: Unsuccessful:
Summary of Changes
This PR loads the fancy-select layout for some multiple lists instead of the default layout.
Testing Instructions
Check views with multiple select fields (contact, some content modules, ...)
Expected result
Fancy-select layout
Actual result
Defualt list layout
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | Administration com_contact Modules Front End |
For me the main reason is, that "normal people" don't know to multi-select with ctrl+mouse (+ definitely the layout)
For normal selects we should use the browser default (+ css) but for multiple select, the browser defaults are still unusable (imho)
Really?
For me we should only be using fancy-select when we need the extra functionality such as the ability to search a very long list. Which at a quick glance is probably true for most of these
| Labels |
Added:
?
|
||
I have tested this item
Tested:
Components:
Contacts (2 elements found)
Modules:
Articles Latest
Articles Most Read
Articles: Newsflash
Banners
Tags: Popular
If I've missed any, please provide list.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/24122.
I have tested this item
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/24122.
| Status | Pending | ⇒ | Ready to Commit |
Status "Ready To Commit".
| Labels |
Added:
?
|
||
| Category | Administration com_contact Modules Front End | ⇒ | Administration com_contact Modules Front End NPM Change |
| Labels |
Added:
NPM Resource Changed
|
||
| Category | Administration com_contact Modules Front End NPM Change | ⇒ | Administration com_contact Modules Front End |
Can we get another test because choices has been updated. Then we can merge it, to get tinymce merged.
Can we get another test because choices has been updated. Then we can merge it, to get tinymce merged.
No Choices update here, I reverted it, I did it on the wrong branch...
I'm going to close this. I disagree with choices becoming the new chosen by using it everywhere. We use it where we need the full functionality (basically tags or searching lists of items)
| Status | Ready to Commit | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2019-04-16 15:27:35 |
| Closed_By | ⇒ | wilsonge | |
| Labels |
Removed:
J4 Issue
|
||
Is there any reason for this other than consistent styling? Because that was the whole reason we ended up with everything being a chosen element. So I think where we can use the browser implementation we should.