>mmmh, "Other" fits libraries/tools better IMO and I'd have problems deciding between "Javascript" and "Javascript in general". but too many options also bewilder, so another Tools/Libraries would probably much for an already packed list.

Tools/Libraries has been added.

>Thing is, tabbing out and perhaps answering later works so well that the case of "new" is surprizing. It is not a big deal, but IMO it points to OOP/containment to be grouped at a wrong level - if encountering such things myself I'd probably put it on a low to middle priority level to fix if general refactoring is in order.

You totally lost me here. What I am saying is that this is an entire application, not like a Web page. So, a lot of invisible processes work in the background and the full interface has to be loaded and used as is in order for things to work. Sometimes, a user would right click a message from a message map to open in a new window. In such circumstances, we cannot garantee its support as the user decided to move it out of the container. It's like I want the car to continue to work even if I remove the wheels.