7 Commits

Author SHA1 Message Date
b3d68c95c5 fix(toggle): use correct toggle background color for iOS colors 2017-04-17 17:49:08 -04:00
93d1d02613 perf(toggle): css containment 2017-04-07 21:06:36 +02:00
c792ab69ae refactor(toggle): checked/activated classes are applied to the host 2017-04-07 21:04:16 +02:00
660d53101f docs(sass): add documentation for the remaining sass variables
closes #8785
2016-12-05 10:16:40 -05:00
750cde38e2 refactor(css): scope component css to mode 2016-09-13 16:52:47 -05:00
55a0257dbc refactor(colors): color should be added as an input instead of directly adding the color to the component
BREAKING CHANGES:

Colors should be passed in the `color` input on components, not added
individually as an attribute on the component.

For example:

```
<ion-tabs primary>
```

Becomes

```
<ion-tabs color=”primary”>
```

Or to bind an expression to color:

```
<ion-navbar [color]="barColor">
   ...
</ion-navbar>
```

```ts
@Component({
  templateUrl: 'build/pages/about/about.html'
})
export class AboutPage {
  barColor: string;

  constructor(private nav: NavController, platform: Platform) {
    this.barColor = platform.is('android') ? 'primary' : 'light';
  }
}
```

Reason for this change:
It was difficult to dynamically add colors to components, especially if
the name of the color attribute was unknown in the template.
This change keeps the css flat since we aren’t chaining color
attributes on components and instead we assign a class to the component
which includes the color’s name.
This allows you to easily toggle a component between multiple colors.
Speeds up performance because we are no longer reading through all of
the attributes to grab the color ones.

references #7467
closes #7087 closes #7401 closes #7523
2016-08-23 17:16:55 -04:00
c8f760f080 chore(build): rename ionic directory to src and update all references in the build process. 2016-05-19 13:22:40 -05:00