[Bug]: 'added' fires when an object is added to a group via .add but not when added via group constructor array.

[drinkspiller]

CheckList

• I agree to follow this project's Code of Conduct
• I have read and followed the Contributing Guide
• I have read and followed the Issue Tracker Guide
• I have searched and referenced existing issues and discussions
• I am filing a BUG report.
• I have managed to reproduce the bug after upgrading to the latest version
• I have created an accurate and minimal reproduction

Version

6.0.2

In What environments are you experiencing the problem?

Chrome

Node Version (if applicable)

None

Link To Reproduction

(2 links, see below)

Steps To Reproduce

1. Create a fabric.Rect instance (or other fabric.FabricObject)
2. Define an on('added', ()>{}) handler for it
3. Add it to a fabric.Group (and add the Group to the canvas and renderAll).

Expected Behavior

A defined on('added', ()>{}) handler will fire whether the FabricObject on which the handler is defined is added to a Group via .add or is added to the group when via the group's objects argument when the Group is constructed.

Actual Behavior

(following reproduction steps above)

If the Rect is added to the group via .add, the added event fires. (demo).

If the Rect is added to the group via the group's objects argument when the Group is constructed, the added event does not fire (demo).

Error Message & Stack Trace

No response

[drinkspiller]

(friendly ping on this)

[asturur]

I know this is 2 months old now and pointless.
I added this doc page for events
https://fabricjs.com/docs/events/

I do think the added event is pointless in general in fabricJS and i m not sure it should fire at all in general, i tried to explain it in that doc between normal documentation.

What was your case for this event? can you point it out?

[drinkspiller]

Alas, I can't recall why I needed it at the time.