Re: RE : inputSuggest : some others improvement to do

[Matt Blum]

Oh, I know that other browsers don't like the iframe fix, and of course it's unnecessary extra code for browsers other than IE anyway.  My _javascript_ code *should* as I say detect that you're using IE (it checks navigator.appVersion, and even makes sure you're not using Opera masquerading as IE), but of course there could very well be a bug I didn't find in my testing.

-Matt

On 8/24/05, Werner Punz <[EMAIL PROTECTED]> wrote:

Matt Blum wrote:
>
>
> On 8/24/05, *Werner Punz* <[EMAIL PROTECTED] <mailto:[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.
>

Ahem given the hard experiences I had with the jsf-comp _javascript_s, I
might say, you even have to detect the ie for the iframe fix, the
problem is that gecko goes haywire if you apply the fix to several gecko
engines, it simply refuses to scroll some parts of the page, although
the iframe did have a size of zero on location 0,0.

Those weird inconsistencies did cost me almost a man day of trying...