Updated EXE and plugins are available here:

http://kmeleon.sourceforge.net/files/test/

Please test against the New and Open bugs reported here (except installer bugs):

http://kmeleon.sourceforge.net/wiki/index.php?id=Beta09

and report back your results. Any other issues? Let us know.

Do you follow thread
http://kmeleon.org/forum/read.php?f=1&i=20079&t=20079
There is information about new Secunia's Window Injection Vulnerability issue, it is confirmed twice that it is affecting to 0.9 Beta 3.
Solution is available at http://mozillanews.org/?article_date=2004-12-08+06-48-46
by setting value dom.disable_window_open_feature.location to 'true'.
Bugzilla bug is available at #273699.

Yes, the beta page has been updated to reflect that.

Solution is available at http://mozillanews.org/?article_date=2004-12-08+06-48-46
by setting value dom.disable_window_open_feature.location to 'true'.

Tools-Browsing Options-Layers Only or Tools-Advanced Preferences-BLOCK sites from altering browser settings sets that pref to 'true', but it still failed the test when I tried it.

Updated EXE and plugins are available

Is there a rough changelog available?

Anything in particular we should/can look out for?

> Yes, the beta page has been updated to reflect that.

Fine, thanks!

Loaded the new exe and kplugins, and went testing.
Clicking on links in the page resulted in the page not being rendered, either in the same window or in a new windows/layer.
Rolled the exe back to a November build and all is well again.
I tried this on numerous sites, including my banking page, and had a 95% failure rate.
Seems something went wrong in the coding.

Yep, indeed, Dec. 7 feels very sluggish.

It isn't possible to use the current beta for day to day surfing, it's broken a bit too much. I don't know what Ulf tried, but selecting text and all key accels break after a few minutes of surfing (and opening and closing some windows) and K-M just displayed the text I typed in from right to left(!) (so, the word "K-Meleon" looked like "noeleM-K" - was that a try on Chinese or UTF-8 support?). K-M's process keeps on running after closing the final window in like 9 out of 10 times.

I just went back to Dec. 1/2.

I have had a menu entry which allows to open Javascript Console in a layer or in a window. It works fine with all the 0.9b3 versions except the last

Here is the modified macro and the menu entries

in menus.cfg

macros(JSConsole, Open JavaScript Console...)
macros(JSCToggle, Open Console in a layer)

in macros.cfg

$jsconsole = "kmeleon.plugins.jsconsole.layer"

JSCToggle{
togglepref(BOOL, $jsconsole); &Sync;
getpref(BOOL, $jsconsole) == "true" ? $tip = "layer" : $tip = "window";
statusbar("Console will opens in a " . $tip);
}

setcheck("macros(JSCToggle)", getpref(BOOL, $jsconsole) ? true:false);

JSConsole{
$xul = "chrome://global/content/console.xul";
getpref(BOOL, $jsconsole) == "true" ? &XUL : open("javascript:");
}

When layer is choosen, it always works
When window is choosen, nothing opens.

I've tried to modify from 'layers only' to 'windows and layers', and to accept the browser modifications ($flip). Impossible.

Where am-I wrong ?

BTW: Was the beta from Dec. 7 so bad that the test dir had to be removed? ;)

Apparently so. Ulf's working on it - hopefully, we'll have something back up in a day or so.

I think the last beta is not so bad. I only find some mini bugs and I didn't have any crash with this version yet.

Any ETA on a new beta?