I filed issue 3644 for this, and am going to get a fix into the 1.6 update.
On Sat, Apr 11, 2009 at 2:29 AM, Gilles B gilles.broch...@gmail.com wrote:
I keep on investigating, if I remove all setEnabled call (TextBox
widget) used to gray not inputable fields (when I display the dialog)
it
I keep on investigating, if I remove all setEnabled call (TextBox
widget) used to gray not inputable fields (when I display the dialog)
it seems to work fine... and IE doesn't freeze.
The dialog contains multiples panels:
1 Vertical panel : the form (defined as main widget of the dialog)
1
I have a problem that seems close to this one. Using GWT 1.6.4 the
problem occurs with IE (6 and 7), not with Firefox, not in local mode,
not with Opera. In the previous version 1.5 I haven't noticed such
bug.
When I close a Popup, my IE freeze and I need to refresh my browser
The JS line in
I made some changes in event handling for 1.6, which might have caused this
(though it's not yet immediately obvious how). I'll be digging into it
tonight -- everyone please update this thread if any more information
surfaces.
On Mon, Mar 30, 2009 at 8:25 AM, nicolas de loof
I'll try to setup a smallest project and reproduce the issue.
On Mon, Mar 30, 2009 at 9:28 PM, Joel Webber j...@google.com wrote:
Still trying to see how this can happen in practice. The only way I can get
the expression !!o.nodeType to give the aforementioned error on IE is to set
o to null
On 26 mar, 19:18, John Tamplin j...@google.com wrote:
On Thu, Mar 26, 2009 at 1:40 PM, Scott Blum sco...@google.com wrote:
That's not good it looks like Nicolas found an object for which trying
to evaluate (!!o.nodeType) throws an exception.
If my atrophied high-school French is
Do you know what event this was? What do you do with the popup to get it to
trigger? Or does it just happen with no user interaction?
On Fri, Mar 27, 2009 at 11:46 AM, nicolas de loof
nicolas.del...@gmail.comwrote:
Some more infos :
We got this exception running in hosted mode browser (with
That's not good it looks like Nicolas found an object for which trying
to evaluate (!!o.nodeType) throws an exception.
@Nicolas:
- What browser is this?
- What are you actually doing to trigger the exception?
- Can you repro it on any popup panel, or is it specific to your app?
On Thu,
On Thu, Mar 26, 2009 at 1:40 PM, Scott Blum sco...@google.com wrote:
That's not good it looks like Nicolas found an object for which trying
to evaluate (!!o.nodeType) throws an exception.
If my atrophied high-school French is correct, I believe the error is that o
is null at that point.
Nice translation ;)
The dev team repported me this error but I'm not working on the module
myself.
I'll try to get more info on how the PopupPanel is used. I think it is part
of the DatePicker but have to confirm.
Must also ask which browser is used in this test.
On Thu, Mar 26, 2009 at 7:18
10 matches
Mail list logo
