After setting up a new machine and doing a fresh install - I was able to deduce that the "Use animations" being disabled was the culprit. I'm assuming other packages might have dependent events and event listeners on their UI elements that get overridden and thus "breaking" their packages.
I'd suggest maybe targeting elements(buttons, inputs, etc) more specifically, rather then simply disabling all transitions/animations on a global scope.
This was first reported in issue https://github.com/silvestreh/atom-material-ui/issues/131- however, we were unable to collectively pin point why certain users could/couldn't reproduce the bugs.
After setting up a new machine and doing a fresh install - I was able to deduce that the "Use animations" being disabled was the culprit. I'm assuming other packages might have dependent events and event listeners on their UI elements that get overridden and thus "breaking" their packages.
The offending style:
I'd suggest maybe targeting elements(buttons, inputs, etc) more specifically, rather then simply disabling all transitions/animations on a global scope.