Comment 1 Jacek Pospychala 2009-08-24 07:02:47 EDT

I can't reproduce this. Maybe simply the page that was accessed was all correct, hence no messages.

Anyway, let's create a simple unit test for this view to make sure we never run into similar bug again.

Comment 2 Jacek Pospychala 2009-08-27 15:46:00 EDT

Unit tests that we have on build server say that there's even 14 messages in Browser Console in scenarios which work correctly for my Windows...

mistery! ;p


expected:<0> but was:<14>

junit.framework.AssertionFailedError: expected:<0> but was:<14>
at org.eclipse.atf.mozilla.ide.ui.console.JavaScriptConsolePageTest.testBrowserConsoleIsEmpty(JavaScriptConsolePageTest.java:69)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206)
at org.eclipse.test.UITestApplication$3.run(UITestApplication.java:195)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3468)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3115)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.test.UITestApplication.runApplication(UITestApplication.java:138)
at org.eclipse.test.UITestApplication.run(UITestApplication.java:60)
at org.eclipse.test.UITestApplication.start(UITestApplication.java:210)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
at org.eclipse.equinox.internal.app.MainApplicationLauncher.run(MainApplicationLauncher.java:32)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
at org.eclipse.core.launcher.Main.main(Main.java:34)

Comment 3 Jacek Pospychala 2009-08-27 15:51:40 EDT

For 1.8.1.3 on Windows results are also different.

Comment 4 Jacek Pospychala 2009-09-03 09:21:53 EDT

I was not able to reproduce scenario where browser console doesn't show messages when it should.
To at least try to avoid such issues in future, we have unit tests verifying now that messages are sent to console for some arbitrary html page.

Marking as FIXED.

Comment 5 Jacek Pospychala 2010-04-09 08:52:51 EDT

Update fixed bugs Target Milestone as part of pre-release bugzilla cleanup.