Releases: mui/material-ui
Releases · mui/material-ui
v0.9.1
General
The following components have been modified to allow for style overrides:
Radio Button Group, Radio Button, Enhanced Switch Label, Text Field, Toggle, Checkbox (#807)
New Components
- List, ListItem, ListDivider, Avatar (#836)
Components
- Checkbox - Added checkedIcon and unCheckedIcon props. This is useful to create icon toggles.
- Dialog - Fixed a bug with the open immediately flag (#810)
- DropDownIcon - Added support for icon ligature (#806)
- Menu - Fixed a style problem (#843)
- RadioButtonGroup - Fixed a bug with mapping Radio children (#820)
- Slider - Fixed a glitch that happened when click on the slider handle (#833)
- TextField - Added fullWidth prop (#827)
- TimePicker
v0.9.0
Breaking
We've cleaned up some of our click/tap events. (#771) Upgrade should be straight forward, please see below:
- DropDownIcon - closeOnMenuItemClick has been replaced with closeOnMenuItemTouchTap.
- Menu - onItemClick has been removed; use onItemTap instead.
- MenuItem - onClick event has been removed; use onTouchTap instead.
General
- ClickAwayable is now bound to onTouchTap instead of onClick (#766)
Components
- AppBar will now render its children (#725)
- DatePicker will now properly handle defaultDate prop changes (#722)
- Dialog actions now respond to onTouchTap (#752)
- LeftNav
- Menu
- RadioButtonGroup can now have its styles overridden (#768)
- RaisedButtons - Fixed a bug that caused incorrect transitions (#731, #702)
- SvgIcon - ViewBox can now be passed in as a prop (#747)
- Tabs - Components inside tabs now keep their state when switching between tabs (#700, #450)
- TextField
- Multi-line text fields can now be initialized with a certain number of rows (#693)
- Fixed style bug that caused width to not be set on disabled text-fields
- Fixed style bug that caused focus underline to be black
- Fixed style problem that caused text to jump on multi-line inputs
- Theme (New)
- This is a high order component that can be used to set your theme overrides (#797)
v0.8.0
Breaking Changes
- Refactored all CSS into Javascript (#30, #316)
- All Material-UI components now have their styles defined inline. This solves
many problems with CSS as mentions in @vjeux's presentation
such as polluting the global namespace with classes that really should be
component specific. In addition to the benefits mentioned in the
presentation, inline styles allow Material-UI to become CSS preprocessor
agnostic and make Themeing much more dynamic and simple.
Read our CSS in JS discussion - Upgrade path:
- If you are overriding component CSS classes: Redefine your overrides as
an object following React's inline styles format,
then pass it into the material-ui component via thestyle
prop. These
changes are applied to the root element of the component. If you are
overriding a nested element of the component, check the component's
documentation and see if there is a style prop available for that nested
element. If a style prop does not exist for the component's nested element
that you are trying to override, submit an issue
requesting to have it added. - If you are using any of Material-UI's Less files: These files have been
refactored into their own javascript files
and can be accessed like sovar FILENAME = require('material-ui').Styles.FILENAME;
.
Material-UI has moved away from being a CSS Framework to being simply a
set of React components.
- If you are overriding component CSS classes: Redefine your overrides as
- All Material-UI components now have their styles defined inline. This solves
- Paper component no longer generates nested divs (#601)
- This allowed us to simplify styling of paper containers. As a result, styling the inner div is no longer necessary.
General
- Themes have been added (#202)
- Requiring individual components is now supported (#363)
- An example would be:
var SvgIcon = require('material-ui/lib/svg-icon);
- The
/lib
folder in Material-UI contains the file structure needed when referencing individual components.
- An example would be:
Components
v0.7.5
v0.7.4
v0.7.3
v0.7.2
General
Components
- Date Picker
- Added
onShow
andonDismiss
props (#399)
- Added
- Dialog
- Flat Button
- Disabled primary buttons use disabled styling over primary (#432)
- Floating Action Button
- Left Nav
- Scrolling is prevented when displayed (#406)
- Menu
- Menu Item
- Added
disable
prop (#402)
- Added
- Overlay
- Now control scroll un/locking. (#406)
- Paper
- Added
innerStyle
prop (#418)
- Added
- Raised Button
- Disabled primary buttons use disabled styling over primary (#432)
- Tabs
- Added
initialSelectedIndex
prop (#389)
- Added
v0.7.1
General
- Allow removal of debug code in production builds (#349)
Components
- AppBar
- Date Picker
- Fixed a bug that caused the date picker dialog window to ghost on small screen widths (#342)
- Dialog Window
- Window no longer loses scroll position after opening a dialog window. (#386)
- DropDown Icon
- Added closeOnMenuItemClick prop (#376)
- Flat Buttons
- Fixed a styling bug with touch ripples.
- Icon Buttons
- Fixed a styling bug with touch ripples. (#341)
- Menu Item
- Link targets can now be set on menu items. (#350)
- Slider
- Fixed percentage calculation in getInitialState (#382)
- Tabs
- The onChange event now passed in the tabIndex, and tab to the callBack (#384)
- Text Field
v0.7.0
Breaking Changes
- Removed Icon component - Replaced with FontIcon and SvgIcon (#318, #125, #148)
- The main motivation here is to give developers more control over which font icons to include
in their project. Instead of automatically including all material design icons in material-ui,
developers can now create their own custom icon font file and just pass the icon className into
the FontIcon component. Read more about FontIcons. - Upgrade path:
- If you were using the Icon component before, you'll need switch to either using FontIcon or SvgIcon.
For FontIcon, create a custom font file and include it in your project and just pass the Icon
className into the FontIcon component. For SvgIcon, create a new React component that represents
that particular icon. This will allow you to package your icons inside your js files. Examples
can be found here. - Additionally, all components that had an icon prop now take an iconClassName prop instead. These
include FloatingActionButton, IconButton, Menu, MenuItem, and DropDownIcon.
- If you were using the Icon component before, you'll need switch to either using FontIcon or SvgIcon.
- The main motivation here is to give developers more control over which font icons to include
General
Components
- Buttons
- Menu Item
- Slider
- Switches
- Tabs
- Fixes width transition for ink bar (#280)
- Text Field