Philippe, Thanks for doing the cleanup. I deliberately refrained from touching individual components :)
However, can you please clarify what is the value of those one-time Bugzilla issues? They do appear in the email notifications, so they produce some noise. Later the end-users would crawl over the fixed bugs listed in the changelog, and they will not know if the bug is a true one or if it is an empty one. So these "empty Bugzilla entries" distract both developers and the end-users :-/ I guess we should commit small UX changes without creating Bugzilla tickets. On the other hand, it would be great to have screenshots (e.g. in the changelog) for the changes. That would be more valuable for the end-users, so they would learn how it works. PS. Some of the components you edit have significant padding around the panel. For instance, While Controller has significant padding for "Conditition (function or variable)" field. I guess we should stick to the following: 1) If a component contains just a set of fields, then padding should be minimal (e.g. like in Debug Sampler where the component panel has no padding around) 2) If there are titled panels, then the padding should be there. For instance, Thread Group has two titled panels, so the contents of the panels is padded. Vladimir
