Remove notes about document.all being readonly#7193
Conversation
These notes were added in mdn#3391, after the change in https://chromium-review.googlesource.com/c/chromium/src/+/823513/. Previously it was possible to assign document.all, and now it is not. The uses of document.all that currently work also work with older browsers, so there isn't anything that web developers need to be aware of here. The only time when it might have mattered was at the time of the change, if someone depending on being able to use document.all to store their own values, which in itself is an unlikely scenario.
github-actions
bot
added
the
data:api
|
It's not clear to me why you're removing this information. We tend not to remove information that is correct even after it ceases to be enabled. (I'm excluding my position on flags here because flags aren't part of the platform.) |
|
I'd say that the reasoning behind the removal is because this property is defined as a read-only property per the spec. The chances of someone wanting to override a property like |
|
What's the story for the specification and the implementation? From #3391, it kinda looks like there was some sort of ambiguity in the spec. That seems interesting enough to note, though I'd probably frame it in historical terms ("Before version 65, this property is assignable… From version 65, the property is readonly, conforming to the updated specification" or something along those lines). I'm trying to imagine a scenario where dropping the note makes sense and I guess it would be if the assignability was undefined in a specification that otherwise defined the behavior of |
|
Before https://chromium-review.googlesource.com/c/chromium/src/+/823513/, it wasn't writable in any interesting way, it was merely possible to replace the object. Compare this do setting The reason that Being replaceable was never an interesting part of the API, and I don't think it's plausible that these notes will be helpful, even if they say something true. |
4 participants
These notes were added in #3391,
after the change in https://chromium-review.googlesource.com/c/chromium/src/+/823513/.
Previously it was possible to assign document.all, and now it is not.
The uses of document.all that currently work also work with older
browsers, so there isn't anything that web developers need to be aware
of here. The only time when it might have mattered was at the time of
the change, if someone depending on being able to use document.all to
store their own values, which in itself is an unlikely scenario.