Success! Looks like we've fixed this one. According to our records the fix was applied for EXTGWT-2547 in 3.0.3.
  1. #11
    Ext GWT Premium Member
    Join Date
    Oct 2010
    Posts
    9
    Vote Rating
    0
    oliver.misch is on a distinguished road

      0  

    Default


    Here a stacktrace from development mode, using GXT 3.0.3:

    Code:
    13:27:22.226 [ERROR] [woe] (Style.java:-1) 2013-01-21 13:27:22,226 [WARN ] An Error Occured: com.google.gwt.core.client.JavaScriptException: (Error) @com.google.gwt.dom.client.Style::setPropertyImpl(Ljava/lang/String;Ljava/lang/String;)([string: 'width', string: '-25.0px']): Ung├╝ltiges Argument. com.google.gwt.core.client.JavaScriptException: (Error) @com.google.gwt.dom.client.Style::setPropertyImpl(Ljava/lang/String;Ljava/lang/String;)([string: 'width', string: '-25.0px']): Ung├╝ltiges Argument. at com.google.gwt.dev.shell.BrowserChannelServer.invokeJavascript(BrowserChannelServer.java:249) at com.google.gwt.dev.shell.ModuleSpaceOOPHM.doInvoke(ModuleSpaceOOPHM.java:136) at com.google.gwt.dev.shell.ModuleSpace.invokeNative(ModuleSpace.java:571) at com.google.gwt.dev.shell.ModuleSpace.invokeNativeVoid(ModuleSpace.java:299) at com.google.gwt.dev.shell.JavaScriptHost.invokeNativeVoid(JavaScriptHost.java:107) at com.google.gwt.dom.client.Style$.setPropertyImpl$(Style.java) at com.google.gwt.dom.client.Style$.setProperty$(Style.java:2030) at com.google.gwt.dom.client.Style$.setPropertyPx$(Style.java:2039) at com.sencha.gxt.theme.base.client.field.TriggerFieldDefaultAppearance.onResize(TriggerFieldDefaultAppearance.java:223) at com.sencha.gxt.cell.core.client.form.TriggerFieldCell.setSize(TriggerFieldCell.java:305) at com.sencha.gxt.widget.core.client.cell.CellComponent.onResize(CellComponent.java:368) at com.sencha.gxt.widget.core.client.Component.setPixelSize(Component.java:848) at com.sencha.gxt.widget.core.client.container.ResizeContainer.applyLayout(ResizeContainer.java:97) at com.sencha.gxt.widget.core.client.form.FieldLabel.doLayout(FieldLabel.java:513) at com.sencha.gxt.widget.core.client.container.ResizeContainer$2.execute(ResizeContainer.java:41) at com.google.gwt.core.client.impl.SchedulerImpl$Task$.executeScheduled$(SchedulerImpl.java:50) at com.google.gwt.core.client.impl.SchedulerImpl.runScheduledTasks(SchedulerImpl.java:228) at com.google.gwt.core.client.impl.SchedulerImpl.flushFinallyCommands(SchedulerImpl.java:327) at com.google.gwt.core.client.impl.Impl.exit(Impl.java:266) at com.google.gwt.core.client.impl.Impl.entry0(Impl.java:257) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:103) at com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:71) at com.google.gwt.dev.shell.OophmSessionHandler.invoke(OophmSessionHandler.java:172) at com.google.gwt.dev.shell.BrowserChannelServer.reactToMessages(BrowserChannelServer.java:293) at com.google.gwt.dev.shell.BrowserChannelServer.processConnection(BrowserChannelServer.java:547) at com.google.gwt.dev.shell.BrowserChannelServer.run(BrowserChannelServer.java:364) at java.lang.Thread.run(Thread.java:662)

  2. #12
    Sencha - GXT Dev Team
    Join Date
    Feb 2009
    Location
    Minnesota
    Posts
    2,734
    Vote Rating
    90
    Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light

      0  

    Default


    oliver.misch, the error message is just the symptom of a bug in the layout system. We can of course fix all exceptions by just wrapping them in try/catch blocks to prevent them from showing error messages, but the real fix is to change the layout so that it makes sense.

    In the original bug here, ContentPanel was misbehaving when it tried to render collapsed. Unfortunately, there isn't enough info in your stack trace to see if there is a ContentPanel present, or if there is another container with the same sort of issue that we missed.

    If we are getting enough issues around this, we might try the try/catch solution to clean this up, but that really should be a last resort - it is always better to treat the underlying issue.