fix(js): add concurrent modification case to "invalid array length" error page

[OnkarRuikar]

The exception is also thrown when array length is changed in a same for loop.

Tested on Google Chrome and Brave.

[github-actions]

Preview URLs

• /en-US/docs/Web/JavaScript/Reference/Errors/Invalid_array_length
• /en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/values

(comment last updated: 2024-05-31 12:22:55)

[Josh-Cena]

I think this should be fixed like this:

• The condition for this error is one and unique: at any time, creating or growing an array to an invalid size. This has 3 sub cases: negative, non-integer, or too big. Negative and non-integer lengths are only achievable by directly setting length or using the constructor, because array methods avoid producing such length values. However, array methods can produce out of bounds lengths, such as pushing to a maxed array, or concating two such arrays. I think it should mention "using a growing array method and producing an array that's too long" as the underlying cause, instead of "concurrent modification", and you should merge it with the other "too big" case.
• "Concurrent modification" in itself does not lead to anything bad. It's because you are doing this endlessly. The current example description is confusing

[farhadfarahi609]

Fix and close all

[farhadfarahi609]

Merging can be performed automatically once the requested changes are addressed.