I have to anonymize this substantially, so forgive the abstraction, but here is the debate.
There is an interface in which you can create an object. This object has several attributes, as well as sub-objects. The sub-objects are what I'm dealing with.
You can add as many sub-objects to an object as you want. You can have zero or 1000, but the realistic range is 1-5.
The sub-objects have a couple of their own attributes. Some of these might be changed once set, but the sub-object title will basically never be changed. Nevertheless, the option to change it must be there.
Deleting a sub-object will be rare except when you accidentally create a new one. A sub-object with entered data will almost never be deleted, and it is decidedly an edge case.
On the page for the main object, you can view its attributes and sub-objects. The sub-objects can be expanded or collapsed.
In order to edit the sub-object title, you must have the sub-object expanded, in which case you'll see an edit icon next to the title. Clicking that icon will turn it into an editable field. Unfocusing from the field makes it revert to fixed text.
When the field is editable, a trash icon appears for the sub-object. When you click the icon, there will be a prompt to confirm you want to delete the sub-object.
In short, this means that, in order to even see the trash icon, you must click once or twice (depending on if the object is expanded). In order to delete, you must make two or three clicks.
That's a lot of clicks, but this is an edge case and I do not want to clutter up the UI with a button that will almost never be used.
Is this the correct solution? If not, what is?
