I have discovered that some SPFx client web parts don't work the same on classic pages as they do on modern pages. I'm currently working with the SPFx Fantastic 40 WebParts. If you try to use the Accordion web part on a classic page, you cannot edit the text, but if you deploy the same web part to a modern page, it works without issues. Is there any MS guidance on what works with the classic pages versus what works with the modern pages?
3
-
hi, spfx webparts that use office ii fabric can work differently on classic apes than they do on modern pages. fabric components that render a button will post back on classic pages, but not modern.– RussGoveApr 13, 2017 at 1:59
-
ha, just checked out of curiosity. that webpart uses ckeditor (ckeditor.com) as a text editor.– RussGoveApr 13, 2017 at 2:14
-
interesting, maft employee using ckeditor. perhaps the need to document how their editor works.– RussGoveApr 13, 2017 at 2:17
Add a comment
|
1 Answer
There is nothing particular. Most parts should work fine, but need to be tested and validated. The SPFx Fantastic 40 isn't developed by the product team. There might be some assumptions made in the F40 code around modern pages that don't translate cleanly.
Are you seeing any errors in the console or the network tab? Might be worth logging an issue in the fantastic 40 github issues list.
