How to properly filter DOM event logs?

One of the new features introduced in Firebug 1.12 alpha 5 is a filter for DOM event logs (issue 229).

Logging of DOM events has been available in Firebug for a long time and the filter should make it more useful and effective in daily usage.

The problem is that we are unsure whether UI/UX of the filter is implemented properly.

So, if you are using this handy feature please read further and let us know what you think (leave a comment below).

Previous Implementation

See the next screenshot, it shows a menu item that represents the Log DOM events feature.

• Log Events feature can be just switched on or off.
• There is no way to pick, which events should be logged for selected node. All events for the node are logged in the Console panel.
• So, there might be a lot of logs in the Console (especially those for mousemove events)

New Implementation

This screenshot shows the new implementation. There is a new submenu that allows to pick what events should be actually logged.

• You can still click the top level Log Events menu to log all events just like before.
• You can also open the submenu and pick only the category of events you are interested at.
• There is a tooltip listing all events in the selected category.
• The tooltip also shows an example of how to use the feature from Firebug's command line.

Questions

• But, is the submenu with event-categories actually needed? Isn't the submenu too long and hard to use?
• Wouldn't it be simpler to keep the feature as it was before and just not log mousemove events? Is anyone actually interested in logging mousemove events?
• Or is there any other and better solution?

What do you think?