Is `JSON.parse source text access` really finished?

[caugner]

Add a description

According to https://github.com/tc39/proposals/blob/main/finished-proposals.md, the JSON.parse source text access proposal is finished and included in the latest spec.

Therefore the proposal have been marked as discontinued in web-specs.

However, JSON.isRawJSON and JSON.rawJSON from that proposal have not actually been added to the latest draft of the specification.

Therefore these features have now been marked as non-standard in browser-compat-data.

However, there is a chance that either the text "included in the latest spec" is inaccurate, or the proposal was inaccurately marked as finished.

[devsnek]

It is in a PR here: tc39/ecma262#3714
I believe it will be merged after the linked tests are complete.

[ljharb]

Yes, it's finished. The PR not yet being merged is irrelevant; the moment it gets stage 4, it's "standard".

[bakkot]

It's a fair point that the description in the "finished proposals" table is wrong though. Probably we should either fix that text or refrain from moving stage 4 proposals to that table until their PR is actually merged.

[ljharb]

ah, that's true - I'll reopen this to track fixing that text.