Postponed (maintainer needs more info)
Project:
Multiselect
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
13 Feb 2012 at 15:46 UTC
Updated:
11 May 2026 at 11:55 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
joshmccormack commentedI tried switching themes and this appears to be related to Adaptive Theme and subthemes of Adaptive Theme. I posted an issue there: http://drupal.org/node/1438908 If you have any advice or guidance it would be appreciated.
Comment #2
nickrice commentedI'm getting the same thing in 6.x-1.7. Exactly the same line of code and char number complained about (ie8).
It's weird that this is reported here less than two weeks ago and I've just searched for it now.
I'm not using the Adaptive theme.
But I am getting this with multiselect and node reference as per above.
I can't say how long I've had the problem - it's possible I haven't even tried it before with ie8 (fine in firefox and chrome and, I've been told, ie9).
Comment #3
nickrice commentedFollowing on from #2: Same error with just a hard-wired list of options and nothing else in the content type.
Comment #4
nickrice commentedOK if I haven't got my wires crossed it seems there was a security update for IE (MS12-010) at around the time this issue was raised. See http://technet.microsoft.com/en-us/security/bulletin/ms12-010
It's dated 14 Feb whereas the issue was raised here on 13 Feb. BUT http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=28839 is dated 10 Feb and refers to the same issue.
So I suspect the update was out before the issue was raised.
So could this be an IE bug that came with the update?
Comment #5
joshmccormack commentedNick - I got that error on IE8 when I was using AdaptiveTheme based themes, but when I switched to Garland or another theme, I didn't get it. Do you experience similar results?
Comment #6
nickrice commentedI'm getting it with Framework on Drupal 6.22.
As the number of choices where multiselect was being used is low my "workaround" has been to switch to using checkboxes.
I thought I smelt a smoking gun with the MS security update about the time the issue was raised, but I would have expected others to have seen and confirmed the issue by now if that were the case. But if MS has issued another update fixing it I wouldn't have noticed due to me changing horses.
I'm no javascript expert, but I find it odd that the error appears to be pure javascript and yet other browsers seem fine with it, the first occurrence of the problem was only noted last month despite plenty of sites using the module, the problem being reported for both 6 and 7, and the module not being updated for almost 2 years (6.x.1.7).
To me that suggests that something has changed and that that change was to something else.
Comment #7
dcolin commentedI made a patch to resolve this Javascript error in IE < 9
Comment #8
Frogtown commentedI can confirm that I was getting this same style of error, where it seemed to have worked a little while back, so not sure if it's an IE8 patch problem or not. But was getting the whole: Object doesn't support this property or method multiselect.js Code: 0 in IE8 and was unable to add or remove objects in my multiselect fields. Worked fine in chrome and firefox.
Using Omega Theme here, and Multiselect 7.x-1.8 -- not dev
I tried the patch, seems to have resolved the problem, I am able to add and remove multiselect items from IE8 in node edit forms again.
Comment #9
pierrepaul commentedThe error is still valid after all this time. Resubmitting the same patch but updated with the new line numbers.
Comment #10
JvE commentedComment #11
mparker17multiselect-7.x-1.x 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.