-
-
Notifications
You must be signed in to change notification settings - Fork 32.3k
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
SelectField works slowly #2859
Comments
Same here - seems like the performance degrades exponentially depending on how many selects are on the screen at once: function generateLocations(locs) {
return locs.map(loc =>
<MenuItem key={loc.ID} value={loc.ID} primaryText={loc.Name} />
);
}
<TableRowColumn colSpan="3" style={selectCellStyle}>
<SelectField onClick={handleTouchTapCancel}
value={currentLocation}
onChange={(e, i, val) => locationHandler(val)} >
{generateLocations(locations)}
</SelectField>
</TableRowColumn> |
I think its also worth mentioning that this issue showed up when we upgraded from 0.13.1 to 0.14.2. |
same issue for me, it's unusable with a list of currencies (150 entries) using 0.14.3 |
Same for me. Have a list with 300 items and it takes 3 seconds to close/open it! |
Is there any way to solve this problem without upgrading whole material ui package to higher(maybe lower) version? I'm experiencing super slow pages because of these select fields. And I cannot figure out what caused this. What should I override to work-around this problem? Can anyone help? For me, it slows the whole page by just being there without opening or closing it. |
Hey guys, We're aware of the performance issues with several components. Rest assured there are plans to address a lot of these issues in the near future. We just want to make sure that we take the right direction when we do so. |
Locking this so people stop +1ing |
Closing in favour of #3289 |
if we have more 10 items, selectfield open menu slowly.
My code For example
The text was updated successfully, but these errors were encountered: