SPFx (Sharepoint Framework) and Rooster React about roosterjs

[romanisa]

Hi, we think this might be an issue at the SharePoint framework side and so we would still urge to get some investigation done on that side first.

[rgcircum]

Hi,
I reported the bug on sp-dev-doc without response ...
SharePoint/sp-dev-docs#9438

SharePoint native richText use CKEditor, But I wanted to use Rooster, too bad.

[JiuqingSong]

If you can provide something that I can debug directly (e.g. a codepen link, or anywhere you deployed your project), I can take a look.

[JiuqingSong]

Close old bug without new replies.

Please feel free to reactive with more info that I can debug with.

[rgcircum]

Sorry for response delay.

All information is in first post (Github repos for test), but, you need a M365 dev plateform (https://developer.microsoft.com/en-us/microsoft-365/dev-program).

Is not reproductible in other context, only Sharepoint/Teams context in SPFx.

VesaJuvonen from SPFx Teams have modified issue on sp-dev-doc repos, but without response.

The bug is not resolved, please re-open de issue.

[JiuqingSong]

The bug is not actionable to us, and for now we are not even sure if it is a bug in roosterjs, unless we have a local repro.

[JiuqingSong]

And as an open source software, if you see any issue that only happens in some special environment, you should debug it from your side and find out the root cause. If it is proved to be a bug of roosterjs, you should be able to build a minimum repro then we can discuss how to fix. Otherwise we have nothing to do with it.