nice one, the interface theme is not a problem, it's just that in firefox it follows the theme used or userchrome and in k-meleon it uses windows own theme. i added it to privacy page and changed the menu location to tools>privacy>cookies manager also added password generator and added an extra menu to the context menu of text input fields. bandwidth tester added under network but unfortunately better gmal2 did not work it functions through jscript and not hostperm. thanks matt.

sorry i misunderstand what you meant.. the autoresize of a dialog or window is handled by firefox xul manipulator so you'll notice that some xul extensions does no include fixed size properties which can cause problems in kmeleon when some of the dialog elemts become outside. this is very easy to fix by explanding the jar and opening the xul with the problem.. in our case it's 'editCookie.xul'

you will find this section in the beginning of the xul..this informs the browser how to draw the dialog:

another problem you might face with some extensions like in edit/add cokies is their prefs file. with some extensions the file name is unique to the extension itself.. no problem there you can use this file as is and add to k-meleon prefs folder but with some extensions the prefs file is not unique and is just named prefs meaning its settings are directly called from fireshit.. but you can't save this file in k-meleon prefs because k-meleon will not understand what to do with it or call the extension's default settings from it.. i see you understood that problem and renamed the file to addneditcookies-preferences.js but k-meleon cannot get the default settings from that file either because the prefs file name must be exactly as the sub category it adds in the browser prefs.js.. in this case it's only 'addneditcookies.js'.

it's very easy to find out the right name for the extension prefs file, you just open that prefs file in notepad and take note of its general setting name.. in that case L