Postponed (maintainer needs more info)
Project:
Multiselect
Version:
7.x-1.8
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
12 Jul 2011 at 20:17 UTC
Updated:
11 May 2026 at 12:09 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
attheshow commentedComment #2
ctotogo commentedYeah, it's definitely having trouble. If I had more time tonight (crazy deadline tomorrow) I'd try to get to the bottom of it, but in the meantime since in each case it's not required in my app, I just added one line to the theme_multiselect function in multiselect.module just before the last line that returns the html as follows:
unset($element['#attributes']['required']);
which just removes it from the mix altogether. A kludge, granted, but will get you past it if you're not concerned about making any of your multiselects required at the moment.
Thanks so much to the author for all your hard work. It's a great module.
-- Carlos
Comment #3
Anonymous (not verified) commentedComment #4
attheshow commentedComment #5
Anonymous (not verified) commentedyour kidding right?!
Comment #6
aron novakAt least it's a major issue. @attheshow: if you have any hints on this, i'm happy to help with coding to fix this.
Comment #7
Depelck commentedThis works in both cases:
Comment #8
mradcliffeThis is a big issue for Firefox 10 and Chrome users using the new HTML 5 client-side validation for multiselect elements generated via FAPI.
The issue is that theme_multiselect() always sets the 'required' attribute in element_set_attributes(). I have attached a patch for review.
git am 0001-Patch-1216808-by-mradcliffe.-Fixes-required-attribut.patchComment #9
Steven Brown commentedIs there a way to use some type of alter function to accomplish this without patching the module? Just curious.
Comment #10
mradcliffeYes, you could implement theme_multiselect() in your custom theme.
Comment #11
max.parker commentedRe-rolling the patch provided by #8 against version 7.x-1.13 of the module.
Comment #12
mparker17multiselect-7.x-1.8 is no longer supported, because Drupal 7 is no longer supported.
Can you confirm if this is still an issue in multiselect-2.0.0-beta4?
I'm going to mark this issue as "Postponed (maintainer needs more info)"... but when you answer, please change it back to "Active". If there is no reply in ~6 months, then I will mark this issue as "Closed (outdated)". Thank you in advance for your understanding and patience as I try to keep this module's issue queue clear.