You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm referring to current 2.4.3 version.
Custom render functions for "optgroup_header" / "optgroup" should also pass $optgroup element in data parameter (in the same way of the "option" and "item" render functions that pass data.$option element).
This could be very usefull for custom styling/icons ecc based on optgroup CSS classes and not on optgroup index/value.
Ex.:
In the select element below I can read "top-position" and "top-destination" classes from the "option" render function using the data.$option parameter, but it seems that there is no way to read SEARCH_D and SEARCH_P classes inside "optgroup_header" and "optgroup" functions.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I'm referring to current 2.4.3 version.
Custom render functions for "optgroup_header" / "optgroup" should also pass $optgroup element in data parameter (in the same way of the "option" and "item" render functions that pass data.$option element).
This could be very usefull for custom styling/icons ecc based on optgroup CSS classes and not on optgroup index/value.
Ex.:
In the select element below I can read "top-position" and "top-destination" classes from the "option" render function using the data.$option parameter, but it seems that there is no way to read SEARCH_D and SEARCH_P classes inside "optgroup_header" and "optgroup" functions.
Beta Was this translation helpful? Give feedback.
All reactions