🦋 Changeset detected

Latest commit: f398551

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

I can't make changes directly on this branch;

Would you be able to

• add a changeset
• cherry-pick the following commit so that the tests pass: c8b0595

The Object.assign bit was introduced in #995
I'm wondering if it had special significance there in terms of how the link element is updated ... have pinged Yun.

@billyvg The only difference is that Object.assign overwrites the attribute value in the mirror. Your change does not change the meta in the mirror.
Can you please help me understand why this difference can cause the bug?

@YunFeng0817 Yeah so I'm not sure if we are relying on changing the meta in the mirror elsewhere. The reason for this change is as follows:

• buildNodeWithSN() is called with the meta from mirror
• Inside of buildNodeWithSN, we check if the meta in mirror is equal to itself

@billyvg Thank you for the clean explanation. I now understand the cause of the issue.
buildNodeWithSN() is called with the meta from mirror I made this for preventing duplicate nodes in the replayer. But a remotely loaded is an exception for the check.

Can you add

Object.assign(
  newSn.attributes,
  mutation.attributes as attributes,
);

to the place after the newNode is created? This can keep the mirror sync with Dom status

@YunFeng0817 Updated!