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
When classic property is true, applying the prettydropdown to a that does not have an with the selected attribute, the plugin renders an unusable empty box. It's easy to work around (for my situation anyway), but like the built in , I think the plugin should default to selecting the first item if one is not selected - or, at minimum, at least allow the dropdown to function.
The text was updated successfully, but these errors were encountered:
Actually... it's not an issue of not having an with the selected attribute, the issue presents when the selected (or first in the list, if none are selected) does not have a value. It's fairly common to have something like <option value="">None</option> or <option value="">Select an option...</option> but these don't work when the classic property is set to true.
When classic property is true, applying the prettydropdown to a that does not have an with the selected attribute, the plugin renders an unusable empty box. It's easy to work around (for my situation anyway), but like the built in , I think the plugin should default to selecting the first item if one is not selected - or, at minimum, at least allow the dropdown to function.
The text was updated successfully, but these errors were encountered: