Describe the bug
Below a list of missing (Beta) Components and Features of the lightning-input-rich-text editor, causing error on local dev server when being used:
Inserting Text Programmatically (Beta)
Inserting Formatted Text Programmatically (Beta)
Adding Custom Buttons (Beta) [and along lightning-rich-text-toolbar-button-group + lightning-rich-text-toolbar-button ]
Observe it fail due to missing components ( lightning-rich-text-toolbar-button-group + lightning-rich-text-toolbar-button )
Expected behavior
Components and features documented should be available in the local dev server unless explicitly stated otherwise. The Beta components are not excluded specifically at Supported and Unsupported Modules, Components, and Features
This said, I would expect the Beta components to be around as part of the latest component build to ensure proper local development and testing new features (even though those are marked as Beta). I would not expect to spam the Org for testing purposes of Beta-Features/Components.
Desktop (please complete the following information):
OS: Windows 10
Browser Chrome
Version 90.0.4430.212
Additional context
We are awaiting changes on the Editor quite some time already. The documentation details look fantastic and I would like to proceed with POCs for that. Unfortunately, rapid and easy development is impossible without those components/features being available in the local dev server. I would have expected those to be part of the latest component build and accessible already.
Describe the bug Below a list of missing (Beta) Components and Features of the
lightning-input-rich-text
editor, causing error on local dev server when being used:lightning-rich-text-toolbar-button-group
+lightning-rich-text-toolbar-button
]To Reproduce
lightning-rich-text-toolbar-button-group
+lightning-rich-text-toolbar-button
)Expected behavior Components and features documented should be available in the local dev server unless explicitly stated otherwise. The Beta components are not excluded specifically at Supported and Unsupported Modules, Components, and Features This said, I would expect the Beta components to be around as part of the latest component build to ensure proper local development and testing new features (even though those are marked as Beta). I would not expect to spam the Org for testing purposes of Beta-Features/Components.
Desktop (please complete the following information):
Additional context We are awaiting changes on the Editor quite some time already. The documentation details look fantastic and I would like to proceed with POCs for that. Unfortunately, rapid and easy development is impossible without those components/features being available in the local dev server. I would have expected those to be part of the latest component build and accessible already.