-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Progress/Spinner not working correctly when React render heavy page #12061
Labels
docs
Improvements or additions to the documentation
good first issue
Great for first contributions. Enable to learn the contribution process.
Comments
I'm closing as a duplicate of #10327 |
Since this is a limitation, maybe we can add some notes in the doc to notify people? |
@HRK44 Yes, we could! Do you want to work on it? :) |
oliviertassinari
added
docs
Improvements or additions to the documentation
good first issue
Great for first contributions. Enable to learn the contribution process.
and removed
duplicate
This issue or pull request already exists
labels
Jul 5, 2018
HRK44
added a commit
to HRK44/material-ui
that referenced
this issue
Jul 5, 2018
On a side note, there is no |
mbrookes
pushed a commit
that referenced
this issue
Jul 5, 2018
acroyear
pushed a commit
to acroyear/material-ui
that referenced
this issue
Jul 14, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
docs
Improvements or additions to the documentation
good first issue
Great for first contributions. Enable to learn the contribution process.
Expected Behavior
The progress should show correctly (spinning, loading, etc...).
Current Behavior
The progress component is not spinning/loading and stays frozen or is very thin (does not render well) when it's a circularprogress.
This is what a circularprogress looks like (size 50) :
Steps to Reproduce (for bugs)
this.state.rendering = true
componentDidMount
or incomponentDidUpdate
tothis.state.rendering = false
render()
function base onthis.state.rendering
Context
Your Environment
The text was updated successfully, but these errors were encountered: