[7.1.0.beta1, SuperDevMode] Uncaught client side exception on addWindow

Vaadin 6 / 7 / 8
1

Hi all, i’d need the
pushMode=automatic
, therefore i’m trying vaadin 7.1.0.beta1 and find a wierd error:

With simple use case:

Button button = new Button("Click Me");
		button.addClickListener(new Button.ClickListener() {
			public void buttonClick(ClickEvent event) {
				Window w = new Window();
				Testvaadin7_1UI.getCurrent().addWindow(w);
			}
		});
		layout.addComponent(button);

It simply open a window.
It has a custom widgetset (the one generated by the eclipse widget, with the default-template widget).

I can compile the widgetset with no error, and it run if i launch it on tomcat.

But, if i run it in superDevMode and in debug mode (?debug), i get “Uncaught client side exception” when i click the button:

(TypeError) : Cannot call method 'replace' of nullcom.google.gwt.core.client.JavaScriptException: (TypeError) : Cannot call method 'replace' of null
	at Unknown.$replaceAll(http://localhost:9876/com.example.testvaadin7_1.widgetset.Testvaadin7_1Widgetset/B875B33A4FDCBD341E2FD257A11B88A1.cache.js@22:111987)
	at Unknown.$getEscaped(http://localhost:9876/com.example.testvaadin7_1.widgetset.Testvaadin7_1Widgetset/B875B33A4FDCBD341E2FD257A11B88A1.cache.js@10:13802)
	at Unknown.format_0(http://localhost:9876/com.example.testvaadin7_1.widgetset.Testvaadin7_1Widgetset/B875B33A4FDCBD341E2FD257A11B88A1.cache.js@19:13820)
	at Unknown.publish_5(http://localhost:9876/com.example.testvaadin7_1.widgetset.Testvaadin7_1Widgetset/B875B33A4FDCBD341E2FD257A11B88A1.cache.js@19:36672)
	at Unknown.$log_1(http://localhost:9876/com.example.testvaadin7_1.widgetset.Testvaadin7_1Widgetset/B875B33A4FDCBD341E2FD257A11B88A1.cache.js@17:14227)
	at Unknown.$log_0(http://localhost:9876/com.example.testvaadin7_1.widgetset.Testvaadin7_1Widgetset/B875B33A4FDCBD341E2FD257A11B88A1.cache.js@5:14212)
	at Unknown.log_5(http://localhost:9876/com.example.testvaadin7_1.widgetset.Testvaadin7_1Widgetset/B875B33A4FDCBD341E2FD257A11B88A1.cache.js@3:14283)
	at Unknown.$log_3(http://localhost:9876/com.example.testvaadin7_1.widgetset.Testvaadin7_1Widgetset/B875B33A4FDCBD341E2FD257A11B88A1.cache.js@20:14344)
	at Unknown.error_1(http://localhost:9876/com.example.testvaadin7_1.widgetset.Testvaadin7_1Widgetset/B875B33A4FDCBD341E2FD257A11B88A1.cache.js@53:32994)
	at Unknown.$createConnectorsIfNeeded(http://localhost:9876/com.example.testvaadin7_1.widgetset.Testvaadin7_1Widgetset/B875B33A4FDCBD341E2FD257A11B88A1.cache.js@9:26694)
	at Unknown.execute_19(http://localhost:9876/com.example.testvaadin7_1.widgetset.Testvaadin7_1Widgetset/B875B33A4FDCBD341E2FD257A11B88A1.cache.js@25:27178)
	at Unknown.runWhenDependenciesLoaded(http://localhost:9876/com.example.testvaadin7_1.widgetset.Testvaadin7_1Widgetset/B875B33A4FDCBD341E2FD257A11B88A1.cache.js@30:25296)
	at Unknown.$handleUIDLMessage(http://localhost:9876/com.example.testvaadin7_1.widgetset.Testvaadin7_1Widgetset/B875B33A4FDCBD341E2FD257A11B88A1.cache.js@3:25847)
	at Unknown.$handleReceivedJSONMessage(http://localhost:9876/com.example.testvaadin7_1.widgetset.Testvaadin7_1Widgetset/B875B33A4FDCBD341E2FD257A11B88A1.cache.js@3:25801)
	at Unknown.$handleJSONText(http://localhost:9876/com.example.testvaadin7_1.widgetset.Testvaadin7_1Widgetset/B875B33A4FDCBD341E2FD257A11B88A1.cache.js@5:25776)
	at Unknown.onResponseReceived_0(http://localhost:9876/com.example.testvaadin7_1.widgetset.Testvaadin7_1Widgetset/B875B33A4FDCBD341E2FD257A11B88A1.cache.js@3:26574)
	at Unknown.$fireOnResponseReceived(http://localhost:9876/com.example.testvaadin7_1.widgetset.Testvaadin7_1Widgetset/B875B33A4FDCBD341E2FD257A11B88A1.cache.js@14:8644)
	at Unknown.onReadyStateChange(http://localhost:9876/com.example.testvaadin7_1.widgetset.Testvaadin7_1Widgetset/B875B33A4FDCBD341E2FD257A11B88A1.cache.js@5:8857)
	at Unknown.

if i disable the debug mode (without ?debug) but still in SuperDevMode the window show up…really only it’s content, with no layout and the window is transparent.
Using chrome debugger “Pause on all exceptions” it halt on :

/**
     * Marks that a ManagedLayout should be layouted horizontally in the next
     * layout phase even if none of the elements managed by the layout have been
     * resized horizontally.
     * 
     * For SimpleManagedLayout which is always layouted in both directions, this
     * has the same effect as {@link #setNeedsLayout(ManagedLayout)}.
     * 
     * @param layout
     *            the managed layout that should be layouted
     */
    public final void setNeedsHorizontalLayout(ManagedLayout layout) {
        assert isAttached(layout); //<------------------------------------------------------ here
        needsHorizontalLayout.add(layout.getConnectorId());
    }

is it a bug ? Why it only happen on SuperDevMode ?

Here’s the use case source code: http://www.mediafire.com/download.php?r0xwjv8hggc0a8a
12964.zip (14.6 KB)