Closed Splaktar closed 8 years ago
This fix didn't make it into 0.10.0 of angular-material. It's been bumped to 0.11.0. Tested today with 0.10.0 and angular 1.4.1 and still have the same problem.
https://github.com/angular/material/issues/2702 was closed as a dupe of https://github.com/angular/material/issues/1559. https://github.com/angular/material/issues/1559 was fixed, but this issue still occurs in Firefox even with 0.11.3 or 0.11.4 of angular-material which contain the supposed fix.
This appears to be due to a bug in angular-material that is slated for the next release, 0.10.0. https://github.com/angular/material/issues/2702