You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 15, 2020. It is now read-only.
See serializeAttributes() where we mangle the JSON attributes in order to provide additional safety against transformations that WordPress might further take.
That is, it's not just "spec JSON" even though it should still be spec compliant. Also, I don't think we've specifically chosen RFC 7159 as our implementation so it may be worth only documenting the level of ambiguity we actually have: we resort to the platform implementation of the JSON parser and serializer.
See serializeAttributes() where we mangle the JSON attributes in order to provide additional safety against transformations that WordPress might further take.
That is, it's not just "spec JSON" even though it should still be spec compliant. Also, I don't think we've specifically chosen RFC 7159 as our implementation so it may be worth only documenting the level of ambiguity we actually have: we resort to the platform implementation of the JSON parser and serializer.
also see…
The text was updated successfully, but these errors were encountered: