search

pnp / sp-dev-fx-controls-react

Reusable React controls for SPFx solutions
https://pnp.github.io/sp-dev-fx-controls-react/
MIT License
380 stars 380 forks source link

SPFx React States issues #306

Closed rafakil closed 10 months ago

rafakil commented 5 years ago

Category

[ ] Enhancement

[ ] Bug

[ x] Question

Version

Please specify what version of the library you are using: [ 15.4 ]

Category

Hello, I get this error when executing my solution that contains 7 SPFx webparts using React 15.4, but just on the customer side , in my side everything works as expected. "Error: Failed to execute 'insertRule' on 'CSSStyleSheet': Failed to parse the rule '@-moz-keyframes animation_do0sdn{from{opacity:0;}to{opacity:1;}}'. I have also an issue about setState, actually each time I need to set the state of my controls (enabled, disabled) I set that using states, on my side it's working fastly, but on the customer side it take about 10 secondes to update the state.

Any suggestions please?

ghost commented 5 years ago

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

michaelmaillot commented 11 months ago

Hi @rafakil,

Do you still have issues with your SPFx solution?

Hard to know what could be the problem without code snippets or details about what contains your solution. It could come from performance issues depending on how is structured the solution, from SPFx Controls, or any other third-party libraries.

ghost commented 10 months ago

This issue has been automatically marked as stale because it has marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within next 7 days of this comment. Thank you for your contributions to SharePoint Developer activities.

ghost commented 10 months ago

Closing issue due no response from original author. If this issue is still occurring, please open a new issue with additional details. Notice that if you have included another related issue as additional comment on this, please open that also as separate issue, so that we can track it independently.