IE rendering issue

I wasn't able to reproduce this using Rubik and IE8.

Similar here with IE 8, using a modified Acquia Marina theme.

IE8 + Compatibility View "fixes" the problem, as does adding the above CSS.

Update: I fixed this by turning off css cache.

I have just seen this on this site on ie8, and not only that but it also doesn't load the variables, so it makes form filling impossible! I tried adding the css width but as I thought, it didn't change anything.

here it is:

http://teaching-practices-contest.elearningeuropa.info/node/add/concurso

not rendering in ie8 and opera either as far as I can see.

Any idea? In IE I also get a JS error not present in Firefox/firebug:

'XPathResult' non è definito js_c4807c31c9123eff72246fe26254de7c.js, Riga 1563 Carattere 2

This line number corresponds to the first uncommented line below: I can uncache and tell you what file that is in, but it might be completely unrelated!

/*************************************************************/

function form_Document_field(){

//var path="/"+[en]{2}+"/node/add/asset";
//var formCount = document.evaluate( 'count(//form[@action="'+path+'"])', document, null, XPathResult.ANY_TYPE, null );
var formCount = document.evaluate( 'count(//div[@id="edit-field-authors-0-uid-uid-wrapper"])', document, null, XPathResult.ANY_TYPE, null );

if (formCount.numberValue>0){

array_documents = new Array("#edit-field-type-asset-value");

for(i=0;i

if($(array_documents[i]).html() != null){
initDocumentInForms(array_documents[i]);
}else{

initDocumentInForms(array_documents[i]);

}

}
}

}

Thanks for any help on this!

Alejandro

This fix is simple (add a width to #multiselect_available to match the select width), so I won't attach a patch, but if you really need one, shoot me an email through my contact form.

#multiselect_available {
float: left;
width: 250px;
}

This fixed the issue for me, in my case I only had to change the width to 220px

Thanks

multiselect-6.x-1.7 is no longer supported, because Drupal 6 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.