Thanks.  Now that I think about it, and have had another cup of coffee (and am therefore genuinely awake), the z-index of the select list wouldn't matter anyway.

There's obviously a bug in the inputSuggest code.  I'll try to find some time tonight to look at it, but may not be able to get to it till the weekend.  If anyone else feels like taking a crack at it in the meantime, I won't be offended. :)

-Matt

On 8/24/05, Clément Maignien <[EMAIL PROTECTED]> wrote:
Sorry but I can't find any z-index in the source ...
Here is what I have :
 
<tbody><tr><td><label for="" entre le </label></td><td>
<input id="receptRechForm:datedebut.day" name="receptRechForm:datedebut.day" size="2" maxlength="2" value="24"/><select id="receptRechForm:datedebut.month" name="receptRechForm:datedebut.month" size="1">  <option value="1">janvier</option>  <option value="2">f&#233;vrier</option>  <option value="3">mars</option>  <option value="4">avril</option>  <option value="5">mai</option>  <option value="6">juin</option>  <option value="7">juillet</option>  <option value="8" selected="selected">ao&#251;t</option>  <option value="9">septembre</option>  <option value="10">octobre</option>  <option value="11">novembre</option>  <option value="12">d&#233;cembre</option></select><input id="receptRechForm:datedebut.year" name="receptRechForm:datedebut.year" size="4" maxlength="4" value="2005"/><script type="text/_javascript_">jscalendarSetImageDirectory("/cormag/faces/myFacesExtensionResource/calendar.HtmlCalendarRenderer/11230381/DB/")</script><script type="text/_javascript_">jscalendarMonthName = new Array("janvier","f&#233;vrier","mars","avril","mai","juin","juillet","ao&#251;t","septembre","octobre","novembre","d&#233;cembre");jscalendarDayName = new Array("lun.","mar.","mer.","jeu.","ven.","sam.","dim.");jscalendarStartAt = 1;
</script><input type='button' value='...'/></td>
-----Message d'origine-----
De : Matt Blum [mailto:[EMAIL PROTECTED]]
Envoyé : mercredi 24 août 2005 16:39
À : MyFaces Discussion
Objet : Re: RE : RE : inputSuggest : some others improvement to do

Yep, that's exactly what I was talking about.  Could you check the z-index of the rendered inputDate component, please, and let me know what it is?

-Matt

On 8/24/05, Clément Maignien <[EMAIL PROTECTED]> wrote:
I use the myfaces-20050802 nightly build. Do I should try with a more recent one ?
 
Here is what I found in the source code (it looks like what you've talk about, no ?) :
 
if (navigator.appVersion.toLowerCase().indexOf('msie') != -1 && navigator.userAgent.toLowerCase().indexOf('opera') == -1)
document.writeln('<iframe id="libarticle_textShim" src="" scrolling="no" frameborder="0" style="position:absolute; top:0px; left:0px;"></iframe>');
 
 
Thanks for youe help Matt.
Clément
-----Message d'origine-----
De : Matt Blum [mailto:[EMAIL PROTECTED]]
Envoyé : mercredi 24 août 2005 15:50
À : MyFaces Discussion; [EMAIL PROTECTED]
Objet : Re: RE : inputSuggest : some others improvement to do



On 8/24/05, Werner Punz <[EMAIL PROTECTED] > wrote:
Clément Maignien wrote:
>     1- I have a small JSF page with an s:inputSuggest component and an
>     t:inputDate component under it.
>     When clicking inside the inputSuggest a dropdown box open and
>     displays firsts suggests. The problem is that under IE (not Firefox)
>     the dropdown-box is displayed behind the inputDate, hiding some
>     suggests.
>
That is a bug in the IE, the fix is to plug an iframe under the panel...
has to be fixed on the _javascript_ side.


Hm.  Curious.  Are you using the latest version of the component?  Sean committed a fix that I implemented for this a while ago, though it's possible it's still buggy.  The _javascript_ code *should* detect that you're using IE and, if so, render an iframe in between the panel and anything under it.

Can you do a View Source on the rendered page, and look for _javascript_ code that looks like it should generate an iframe with an id ending in the string "Shim"?  If it's there, could you check the z-index of the rendered inputDate component?  If the iframe's not there, or is there but not rendering, you're either using an old version of the code, or there's a bug I don't know about.  If it's there and rendering, but you're still seeing that behavior, I may need to tweak the z-index calculations.  Please let me know, as I don't have time at the moment to test it myself.

-Matt



Reply via email to