This is exactly the case! Thanks so much - the workaround works
amazingly well! I did think about the same thing myself but kinda mist
out that you should set 100% height on html, otherwise body will count
its 100% from parent... Thanks again - you saved me a day of
googling... I wish gwt guys added stuff like that to the official FAQ
or javadoc... I am sure it is more than useful as the new Layout
panels require standards mode...

On Mar 25, 11:30 am, Thomas Broyer <[email protected]> wrote:
> On Mar 25, 10:02 am, Michail Prusakov <[email protected]>
> wrote:
>
>
>
> > I've recently tried out the SuggestBox widget. I've used the following
> > code, which I took from javadoc:
>
> >   MultiWordSuggestOracle oracle = new MultiWordSuggestOracle();
> >   oracle.add("Cat");
> >   oracle.add("Dog");
> >   oracle.add("Horse");
> >   oracle.add("Canary");
>
> >   SuggestBox box = new SuggestBox(oracle);
> >   RootPanel.get().add(box);
>
> > If I type, say 'h', in the text box the suggestion list appears
> > correctly. If I click somewhere beneath the box in Firefox the list
> > disappears as expected. If I do the same in IE8 the list does not
> > disappear. If I turn the quirks mode, everything works correctly.
>
> > As far as I understand the problem is not just with SuggestBox as it
> > uses a PopupPanel which in turn registers a NativePreviewHandler which
> > does not seem to receive an event.
>
> > I have tried both: gwt 1.7.1 and 2.0 and got the same results.
>
> > So is this a simple bug which will be fixed at some point or a serious
> > technological limitation?
>
> Could it be that you're clicking within the "viewport" but outside the
> document's "body"? As Internet Explorer doesn't support registering
> event listeners in the "capture" phase, GWT registers handlers on the
> document.body to "capture" (almost) every event and explicitly
> "previews" every event before dispatching it to the widget; while in
> all other browsers an event listener is registered on the window (not
> the document.body, the window!) in the capture phase.
> And IIRC, in quirks mode the body is sized so that it's never
> "smaller" than the viewport, which is not the case in standards mode
> by default. A workaround is (IIRC) to add the following to your
> stylesheet:
> html { height: 100%; }
> body { height: 100%; }
> but be aware that it might affect others browsers too...
>
> I have this same problem in an Enterprise app where all users are
> forced to use IE6 (crappy corporate rules!). When they reported the
> bug, I told them that it just doesn't work if you click the blank area
> below the content; and they haven't asked us to "fix it".

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Reply via email to