[BUGFIX] Setting ArrayProxy#content in willDestroy resets length. #16784
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prior to this change,
ArrayProxy.prototype.length
was marked as dirty (and therefore recomputed) whencontent
was set due toarrangedContent
being an alias ofcontent
, andArrayProxy
implementingPROPERTY_DID_CHANGE
to traparrangedContent
changes.Unfortunately,
notifyPropertyChange
avoids notifying some things when the object is destroying. This results in the preexistingPROPERTY_DID_CHANGE
trap forarrangedContent
is no longer called, and thereforelength
is never marked as dirty.This fixes the condition, by implementing a
content
trap inPROPERTY_DID_CHANGE
that marks length as dirty. The next time thatlength
is accessed it will do the normal work to recalculate./cc @krisselden @runspired