With only one layer when I select "close layer", the whole browser closes. (Previously it just turned the active layer to a blank one.) Then, when I open KM again, it starts with TWO layers, one blank one titled K-Meleon, and another blank titled about:blank (yeah, it's set to open with a blank page). This can't be intentional. (Running Win98 and build 844, of course.)

Just happened to me now.
In fact, KM is not closed, closing the layer fails and KM is hidden from the user. When you start KM again (thinking it is not running) it finds the hidden process and add a new tab to it.

Please file a bug on this and the steps to replicate it.

can't reproduce it
sorry

Huh?

To me it happens every time I close a layer if I only have one open!

Yep, the cause is just as Marc said, it actually just closes the layer, which is in fact the whole window, but doesn't close KM itself... This did not happen in earlier builds. I wonder if some safety has been removed from the code or something?

In my case it didn't close the layer. When KM reappeared, the one I wanted to closed was still there. The second layer was there too, and a new one (about:blank) has been added.

I can't make it do that at all! Mine retains the blank layer and stays put. I tried hard, too, using different menus and keys :-)

I think it's a bug that happens when user_pref("kmeleon.plugins.layers.catch", true); is enabled, because I don't have the problem now that is disabled.

Rob

I confirm, this bug happens only when user_pref("kmeleon.plugins.layers.catch", true); is enabled.
KM build 844, Win ME.

The preference wasn't set in either way in my settings. What is the default behavior?

Default is false. (ie. opens new windows and not layers.)

Yes, and I have it set to true as well, so it's quite possible it only occurs if this is the case.

It happened to me, and the pref was set to default (which, you're saying, is false)

Hmm, and if I understood your earlier post correctly, you had at least two layers open when it happened to you? So it seems the result was the same, but the circumstances somewhat different... weird...

Yes, very weird. And I can't reproduce it.