This package is a sample kit of Client Side Web Parts built on the SharePoint Framework SPFx. You can find here different kind of high visual web parts as carousel, images galleries, animations, map, editors, etc.
I have tested almost all the components in classic and modern pages and I have found that most of them only work in modern pages. For instance, none of the chart web parts work in classic pages, nor does the message bar, accordion, tabs, news slider, and several others that could be of prime value on my current SPO tenant. The error message is usually "failed to load url. There may be a problem with the HTTPS certificate" This only occurs on classic pages. On modern pages there are no issues. Can you account for the difference in behavior between classic and modern pages. Are there design guideline for the two scenarios for creating SPFx web parts?
I have tested almost all the components in classic and modern pages and I have found that most of them only work in modern pages. For instance, none of the chart web parts work in classic pages, nor does the message bar, accordion, tabs, news slider, and several others that could be of prime value on my current SPO tenant. The error message is usually "failed to load url. There may be a problem with the HTTPS certificate" This only occurs on classic pages. On modern pages there are no issues. Can you account for the difference in behavior between classic and modern pages. Are there design guideline for the two scenarios for creating SPFx web parts?