RestrictedMode field definition - has it become obsolete?

[MathieuMarchant]

What type of issue is this?

Documentation issue / typo

What SharePoint development model, framework, SDK or API is this about?

Declarative list formatting

Target SharePoint environment

SharePoint Online

What browser(s) / client(s) have you tested

• 💥 Internet Explorer
• 💥 Microsoft Edge
• 💥 Google Chrome
• 💥 FireFox
• 💥 Safari
• mobile (iOS/iPadOS)
• mobile (Android)
• not applicable
• other (enter in the "Additional environment details" area below)

Additional environment details

• Google Chrome Version 111.0.5563.148

Issue description

The documentation of RestrictedMode states the following:
https://github.com/SharePoint/sp-dev-docs/blob/main/docs/schema/field-element-field.md#attributes

RestrictedMode	Optional Boolean. TRUE to not allow the Note field to contain enhanced rich text formatting, such as pictures, tables, or hyperlinks, nor to allow pasting formatted text into the field.

However when creating both a "Plain Text" and an "Enhanced rich text" multiple lines of text field, in the SchemaXml defintion the RestrictedMode is nowhere to be seen. It seems as if the rich text properties of a Note field are purely defined by the RichtText boolean field and the RichTextMode.

If so, can it be clearly pointed out that "RestrictedMode" has become obsolete? Or if it hasn't, can it be cleared out in which scenario it should be used or why it is there?

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[MathieuMarchant]

@juliemturner was already so kind to clarify this in the pnpjs repo. Maybe this can be incorporated in the documentation as well?
pnp/pnpjs#2637

[github-actions]

Thank you for taking the time to file an issue. We periodically archive older or inactive issues as part of our issue management process, which automatically closes them once they are archived.

If you’d like to understand more about why and how we handle archived (closed) issues, please see Our approach to closed issues.

We appreciate your contribution and if this is still an active issue with the latest SPFx versions, please do resubmit the details. We needed to perform a cleanup, so that we can start with a clean table with a new process. We apologize for the inconvenience this might cause.