Selection behavior for duplicate component

[edschema]

Description
If a structural or content block is used twice within a parent block, clicking on one selects both instances. See screenshot below:

This may be a problem in the case where an educator accidentally adds the same block twice. If the block is then clicked and removed from the structural block because the intent was to have the block once, both instances will be removed.

Desired Behavior
In the case of multiples of the same component being used in one structural block, clicking that block should select only one instance of the block. Clicking "remove" from the overflow menu should remove only one instance at a time.

[ahtesham-quraish]

@edschema can you please let me know the reproduction steps?

[edschema]

• in a content library, create a unit
• within that unit, create text component A
• after creating, click "add existing" content
• find text component A and add.
• there should be two instances of text component A in the unit. click on one. you will see both selected.

[ahtesham-quraish]

@edschema the reason of this behaviour is that when we add the same component A multiple time then because the id of the component is same which causes this behaviour so upon selection of the component multiple same components got selected because of same id. @bradenmacdonald can you please suggest here what should we do in this case?

[bradenmacdonald]

@ahtesham-quraish The simplest solution is likely to make the HTML id a combination of the usage key and the index (position) in the container. But if the component's UUID is available, we could also use that.

[navinkarkera]

We already have id and index combination here to support drag and drop, I'll use it for selection and delete operation as well.

[ChrisChV]

Hi @jmakowski1123 @sdaitzman @edschema this is ready for AC testing on the sandbox

[edschema]

This is working as expected for all levels: ss within sections, units withing ss, components within units. Thank you!