AngularJS Material: Material Design component library for AngularJS (1.x). Use angular/material2 channel for Angular Material (v2+).
Splaktar on master
fix(toast): apply theming corre… perf(icon): better handling of … fix(list): copy ng-show, ng-hid… and 49 more (compare)
Splaktar on v1.1.0-rc.5
release: version 1.1.0-rc.5 (compare)
Splaktar on master
feat(panel): initial implementa… update(panel): promise logic im… update(panel): add and remove p… and 44 more (compare)
Splaktar on v1.1.0-rc4
release: version 1.1.0-rc4 (compare)
Splaktar on v1.1.0-rc3
release: version 1.1.0-rc3 (compare)
Splaktar on es6-tutorial
Prepare clean start Remove bow… install angular-material And i… working version of starter-app and 19 more (compare)
Splaktar on master
Tutorial Readme updates Updates for Tutorial #2 Update README with tutorial ste… and 56 more (compare)
Splaktar on fixBlurryRightNavIe11
fix(sidenav): rightNav button a… (compare)
Splaktar on master
fix(dialog): don't clobber md-d… update version number in packag… update(changelog): sort so 1.1.… and 1 more (compare)
Splaktar on fixSideNavDemo
docs(sidenav): leftNav text isn… (compare)
Splaktar on fixSideNavDemo
docs(sidenav): invalid `md-whit… (compare)
Splaktar on master
update(changelog): add missing … fix(toolbar): remove transition… fix(tests): Cleans up the DOM a… and 2 more (compare)
Splaktar on master
update(docs): improve docs for … update(docs): renamed `md-text-… fix(list): clickable list-items… and 71 more (compare)
Splaktar on improveExtendThemeDoc
update(docs): improve docs for … (compare)
Splaktar on improveExtendThemeDocs
update(docs): improve docs for … (compare)
Splaktar on updateThemingDocs
update(docs): renamed `md-text-… (compare)
Splaktar on master
fix(demo, codepen): use secure … fix(build, layout): remove depr… update(build): remove stale bow… and 72 more (compare)
Splaktar on v1.1.0-rc2
release: version 1.1.0-rc2 (compare)
Splaktar on master
fix(checkbox): pointer events d… update(tests): remove disabled/… fix(datepicker): enable scrolli… and 20 more (compare)
Splaktar on v1.0.6
Revert "fix(select): made selec… update(layout): add layout-nowr… fix(whiteframe): update breakpo… and 57 more (compare)
screenfull
that applies the HTML5 spec to full screen the image.@masber_twitter looking at this:
https://github.com/angular/material2/blob/master/src/lib/stepper/stepper-vertical.html
and
https://github.com/angular/material2/blob/master/src/cdk/stepper/stepper.ts
looks like click is called and executes step.select() … neither have logic to disable the events. Also i dont see a good way with angular.
So you will either have to overwrite one of the material classes or make your own.
@roeldeveloper28
this is not the best option, but you can extend theirs and give it a container. I did this here for the snacker
https://stackblitz.com/edit/angular-material-tooltip-in-container-2?file=app%2Fdynamic-overlay-container%2Fdynamic-snack-bar.ts
the only issue is you have to keep it up to date with the latest version.
Hi
can anyone help me to listen scroll
event on mat-autocomplete
overlay box
Template code
<input matInput placeholder="Notebook Page" formControlName="notebookPage" [matAutocomplete]="NBPageAutocomplete" >
</mat-form-field>
<mat-autocomplete #NBPageAutocomplete="matAutocomplete" cdkScrollable >
<mat-option *ngFor="let option of suggestedNBPageNames" [value]="option">
{{ option }}
</mat-option>
</mat-autocomplete>
component code
import { ScrollDispatcher } from '@angular/cdk/overlay';
constructor(public scroll: ScrollDispatcher) {}
ngAfterViewInit() {
this.scroll.scrolled().subscribe((data: CdkScrollable) => {
console.log(data);
//make an HTTP call when it reaches to the end, to add some more data
});
}
When imported only into main app that imports the feature module, the feature module's components are no longer styled with angular material and instead look like plain unstyled html.
When imported only in the feature module and not the main app, the main app fails to load due to using angular material components in the component templates.
Usage:
<app-custom>
<mat-error>custom error</mat-error>
</app-custom>
In Custom component:
<mat-form-field>
<input .../>
<ng-content select="mat-error, mat-hint"></ng-content>
</mat-form-field>
Is there something I'm missing?
Hey people
I am working on a project where we would like our designers to be able to theme angular-material. Not just the colours, but other aspects that would reflect our brand and unique challenge. Sometimes at a component level, but a lot of the time at a project wide level.
We would also like to be able to customise the Angular Material docs to create a living style guide that also contains our custom components/extensions as well as other information and standards that are used for our specific project.
How do others here approach the situation or suggest approaching it?
mat-error
to the custom component in the mat-form-field
as you would normally then add your <ng-content select=“[‘mat-error’]”></ng-content>
. When consuming your component you would add mat-error
as if you were using a mat-form-field