Bug #11172
closed
Select2 should be initialized explicitly
Added by Marek Hulán over 9 years ago.
Updated over 6 years ago.
Description
After select2 was merge, we saw issues with ajax loaded forms. We have workarounds that initialize select2, destroy it and reinitialize it later. When a poor plugin developer wants have control over forms we don't provide any way how to customize this.
I think we should call initialize select2 only on select fields that have specific class.
- Related to Bug #11171: Select2 does not work with compute profiles added
- Related to Bug #11173: Multi-select should be initialized explicitly added
- Description updated (diff)
Perhaps a class to exclude it would be easier, and then less likely to cause inconsistencies (because somebody forgot to add a class, or a plugin hasn't done it yet)?
Yeah, and we already use it in places.
- Status changed from New to Ready For Testing
- Assignee set to Tomer Brisker
- Translation missing: en.field_release set to 35
- Pull request https://github.com/theforeman/foreman/pull/2592 added
- Pull request deleted (
)
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Also available in: Atom
PDF