Michał Dudak

Sure, this wasn't my main motivation anyway. The primary use cases I had in mind were: 1. Eliminate the unnecessary classes when styling Base components with a solution like Tailwind...

Is it still happening? The package seems to be published correctly to npm (https://www.npmjs.com/package/@mui/core-downloads-tracker), so it looks like an npm issue. I also wasn't able to reproduce the issue locally

@prankurnov15 feel free to take it. It's not assigned to anyone.

@kanishbodhwani do you have an idea of how you'd like to fix the problem? The number input has some inherent issues, and its behavior differs across browsers. There's a good...

It's not just about "e". There are other characters ("+", "-", ".") that can make the input value invalid when misused. IMO recommending not to use `type="number"` would be the...

As stated in the description of the issue and the article I linked, other browsers behave differently. In Firefox, for example, you can type any character. While I appreciate your...

@jesrodri what idea do you have for solving this? @shehand-xino, please open another issue with a reproduction on codesandbox so we can reproduce this bug.

I think the "good first issue" label wasn't too accurate, to say the least. This is a pretty complicated problem, and we need to discuss the possible solutions that will...

I resolved the conflicts caused by the recent prop renaming.

Could you please merge in the latest master? Codecov shows something weird.