Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Material2 Doesn't seem to work with Angular 2 RC 2 #693

Closed
naveedahmed1 opened this issue Jun 15, 2016 · 9 comments
Closed

Material2 Doesn't seem to work with Angular 2 RC 2 #693

naveedahmed1 opened this issue Jun 15, 2016 · 9 comments

Comments

@naveedahmed1
Copy link

Angular Material 2 doesn't seems to work with RC 2.

I made changes to my packages.json and have below dependencies:

"@angular/common": "^2.0.0-rc.2",
    "@angular/compiler": "^2.0.0-rc.2",
    "@angular/core": "^2.0.0-rc.2",
    "@angular/http": "^2.0.0-rc.2",
    "@angular/platform-browser": "^2.0.0-rc.2",
    "@angular/platform-browser-dynamic": "^2.0.0-rc.2",
    "@angular/router": "^2.0.0-rc.2",

    "@angular2-material/core": "2.0.0-alpha.5",
    "@angular2-material/button": "2.0.0-alpha.5",
    "@angular2-material/card": "2.0.0-alpha.5",
    "@angular2-material/checkbox": "2.0.0-alpha.5",
    "@angular2-material/grid-list": "2.0.0-alpha.5",
    "@angular2-material/icon": "2.0.0-alpha.5",
    "@angular2-material/input": "2.0.0-alpha.5",
    "@angular2-material/list": "2.0.0-alpha.5",
    "@angular2-material/progress-bar": "2.0.0-alpha.5",
    "@angular2-material/progress-circle": "2.0.0-alpha.5",
    "@angular2-material/radio": "2.0.0-alpha.5",
    "@angular2-material/sidenav": "2.0.0-alpha.5",
    "@angular2-material/slide-toggle": "2.0.0-alpha.5",
    "@angular2-material/tabs": "2.0.0-alpha.5",
    "@angular2-material/toolbar": "2.0.0-alpha.5",

But when I try to restore packages, I receive below error:

@angular2-material/[email protected] requires a peer of @angular/[email protected] but none was installed

@jelbourn
Copy link
Member

The peer dependency thing is just a warning. Does it actually not work?

@aquinum6
Copy link

I don't know about alpha.5 because I'm using alpha.5-2 (you should update).

RC2 and alpha.5-2 seems to work quire fine (i'm using this two together right now).
I just noticed one issue which I posted in: #696

@medeirosrich
Copy link

I get the same error (using 2.0.0-alpha.5-2) but my application seems to be running fine.

Just ignore it I suppose

@jelbourn
Copy link
Member

Closing this for now since people can just ignore the warnings.

@naveedahmed1
Copy link
Author

You are right, application seems to be working despite of these warnings, I need to test it with new form with disableDeprecatedForms()

@naveedahmed1
Copy link
Author

naveedahmed1 commented Jun 18, 2016

@jelbourn it seems that material form controls are not working with Angular 2 RC 2. I am receiving

EXCEPTION: No value accessor for 'firstName'.

I have tested it on md-input, md-slide-toggle and md-checkbox and I receive below exception on all of them.

EXCEPTION: No value accessor for 'Field name'.

Can you please check and reopen this issue.

@aquinum6
Copy link

#696

I posted this issue already.

@naveedahmed1
Copy link
Author

Ok, thanks Piotr, I will follow that.

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 5, 2019
alexeagle pushed a commit to alexeagle/material2 that referenced this issue Nov 6, 2024
* build: enable codelyzer and most default Angular CLI TSLint rules

- do some merging of tslint:recommended and our rules

* fix(a11y): fix theme picker keyboard access

enable Codelyzer a11y rules

Relates to angular#671

* fix(component-overview): header does not show up in headings list

Fixes angular#695

* fix(stack-blitz-button): no accessible label and description is not on correct element

Fixes angular#693

* fix(example-viewer): no accessible label on View source button

Fixes angular#693

* fix(component-sidenav): apply aria-current to selected nav items & improve contrast

- use Roboto font instead of system-ui for `docs-nav-content-btn`s
- use a different background color for selected route, in addition to different text color
- increase opacity of `docs-nav-content-btn`s to meet contrast guidelines
- switch to `mat-nav-list` to get the benefits of better contrast and hover/focus styles
  - plus slightly more padding for touch interfaces

Fixes angular#694. Relates to angular#671.

* fix: use header and main tags for more semantic HTML

- improves screen reader support
- footer tags were already properly used

Relates to angular#671.

* fix(component-nav): apply aria-label to navs

- so that they can be differentiated by screen readers

Relates to angular#671.

* fix(component-nav): remove aria-label that duplicates messages

- aria-expanded already covers whether the section can be toggled or not
- the button's text content already covers the accessible name

Relates to angular#671.

* fix(header-link): remove title

- the aria-label is sufficient

Relates to angular#671.

* feat(theme-picker): provide a visual preview of the theme colors via an SVG

* fix(theme-picker,version-picker): add/improve aria-labels and tooltips

Fixes angular#671

* fix: various a11y refinements

- minify theme-demo-icon.svg
- use & instead of / as it reads better on a screen reader
- prefix classes with `docs-`
- tell screen reader users when a theme has been selected

Fixes angular#671
alexeagle pushed a commit to alexeagle/material2 that referenced this issue Dec 12, 2024
* build: enable codelyzer and most default Angular CLI TSLint rules

- do some merging of tslint:recommended and our rules

* fix(a11y): fix theme picker keyboard access

enable Codelyzer a11y rules

Relates to angular#671

* fix(component-overview): header does not show up in headings list

Fixes angular#695

* fix(stack-blitz-button): no accessible label and description is not on correct element

Fixes angular#693

* fix(example-viewer): no accessible label on View source button

Fixes angular#693

* fix(component-sidenav): apply aria-current to selected nav items & improve contrast

- use Roboto font instead of system-ui for `docs-nav-content-btn`s
- use a different background color for selected route, in addition to different text color
- increase opacity of `docs-nav-content-btn`s to meet contrast guidelines
- switch to `mat-nav-list` to get the benefits of better contrast and hover/focus styles
  - plus slightly more padding for touch interfaces

Fixes angular#694. Relates to angular#671.

* fix: use header and main tags for more semantic HTML

- improves screen reader support
- footer tags were already properly used

Relates to angular#671.

* fix(component-nav): apply aria-label to navs

- so that they can be differentiated by screen readers

Relates to angular#671.

* fix(component-nav): remove aria-label that duplicates messages

- aria-expanded already covers whether the section can be toggled or not
- the button's text content already covers the accessible name

Relates to angular#671.

* fix(header-link): remove title

- the aria-label is sufficient

Relates to angular#671.

* feat(theme-picker): provide a visual preview of the theme colors via an SVG

* fix(theme-picker,version-picker): add/improve aria-labels and tooltips

Fixes angular#671

* fix: various a11y refinements

- minify theme-demo-icon.svg
- use & instead of / as it reads better on a screen reader
- prefix classes with `docs-`
- tell screen reader users when a theme has been selected

Fixes angular#671
alexeagle pushed a commit to alexeagle/material2 that referenced this issue Dec 16, 2024
* build: enable codelyzer and most default Angular CLI TSLint rules

- do some merging of tslint:recommended and our rules

* fix(a11y): fix theme picker keyboard access

enable Codelyzer a11y rules

Relates to angular#671

* fix(component-overview): header does not show up in headings list

Fixes angular#695

* fix(stack-blitz-button): no accessible label and description is not on correct element

Fixes angular#693

* fix(example-viewer): no accessible label on View source button

Fixes angular#693

* fix(component-sidenav): apply aria-current to selected nav items & improve contrast

- use Roboto font instead of system-ui for `docs-nav-content-btn`s
- use a different background color for selected route, in addition to different text color
- increase opacity of `docs-nav-content-btn`s to meet contrast guidelines
- switch to `mat-nav-list` to get the benefits of better contrast and hover/focus styles
  - plus slightly more padding for touch interfaces

Fixes angular#694. Relates to angular#671.

* fix: use header and main tags for more semantic HTML

- improves screen reader support
- footer tags were already properly used

Relates to angular#671.

* fix(component-nav): apply aria-label to navs

- so that they can be differentiated by screen readers

Relates to angular#671.

* fix(component-nav): remove aria-label that duplicates messages

- aria-expanded already covers whether the section can be toggled or not
- the button's text content already covers the accessible name

Relates to angular#671.

* fix(header-link): remove title

- the aria-label is sufficient

Relates to angular#671.

* feat(theme-picker): provide a visual preview of the theme colors via an SVG

* fix(theme-picker,version-picker): add/improve aria-labels and tooltips

Fixes angular#671

* fix: various a11y refinements

- minify theme-demo-icon.svg
- use & instead of / as it reads better on a screen reader
- prefix classes with `docs-`
- tell screen reader users when a theme has been selected

Fixes angular#671
alexeagle pushed a commit to alexeagle/material2 that referenced this issue Dec 18, 2024
* build: enable codelyzer and most default Angular CLI TSLint rules

- do some merging of tslint:recommended and our rules

* fix(a11y): fix theme picker keyboard access

enable Codelyzer a11y rules

Relates to angular#671

* fix(component-overview): header does not show up in headings list

Fixes angular#695

* fix(stack-blitz-button): no accessible label and description is not on correct element

Fixes angular#693

* fix(example-viewer): no accessible label on View source button

Fixes angular#693

* fix(component-sidenav): apply aria-current to selected nav items & improve contrast

- use Roboto font instead of system-ui for `docs-nav-content-btn`s
- use a different background color for selected route, in addition to different text color
- increase opacity of `docs-nav-content-btn`s to meet contrast guidelines
- switch to `mat-nav-list` to get the benefits of better contrast and hover/focus styles
  - plus slightly more padding for touch interfaces

Fixes angular#694. Relates to angular#671.

* fix: use header and main tags for more semantic HTML

- improves screen reader support
- footer tags were already properly used

Relates to angular#671.

* fix(component-nav): apply aria-label to navs

- so that they can be differentiated by screen readers

Relates to angular#671.

* fix(component-nav): remove aria-label that duplicates messages

- aria-expanded already covers whether the section can be toggled or not
- the button's text content already covers the accessible name

Relates to angular#671.

* fix(header-link): remove title

- the aria-label is sufficient

Relates to angular#671.

* feat(theme-picker): provide a visual preview of the theme colors via an SVG

* fix(theme-picker,version-picker): add/improve aria-labels and tooltips

Fixes angular#671

* fix: various a11y refinements

- minify theme-demo-icon.svg
- use & instead of / as it reads better on a screen reader
- prefix classes with `docs-`
- tell screen reader users when a theme has been selected

Fixes angular#671
josephperrott pushed a commit that referenced this issue Dec 18, 2024
* build: enable codelyzer and most default Angular CLI TSLint rules

- do some merging of tslint:recommended and our rules

* fix(a11y): fix theme picker keyboard access

enable Codelyzer a11y rules

Relates to #671

* fix(component-overview): header does not show up in headings list

Fixes #695

* fix(stack-blitz-button): no accessible label and description is not on correct element

Fixes #693

* fix(example-viewer): no accessible label on View source button

Fixes #693

* fix(component-sidenav): apply aria-current to selected nav items & improve contrast

- use Roboto font instead of system-ui for `docs-nav-content-btn`s
- use a different background color for selected route, in addition to different text color
- increase opacity of `docs-nav-content-btn`s to meet contrast guidelines
- switch to `mat-nav-list` to get the benefits of better contrast and hover/focus styles
  - plus slightly more padding for touch interfaces

Fixes #694. Relates to #671.

* fix: use header and main tags for more semantic HTML

- improves screen reader support
- footer tags were already properly used

Relates to #671.

* fix(component-nav): apply aria-label to navs

- so that they can be differentiated by screen readers

Relates to #671.

* fix(component-nav): remove aria-label that duplicates messages

- aria-expanded already covers whether the section can be toggled or not
- the button's text content already covers the accessible name

Relates to #671.

* fix(header-link): remove title

- the aria-label is sufficient

Relates to #671.

* feat(theme-picker): provide a visual preview of the theme colors via an SVG

* fix(theme-picker,version-picker): add/improve aria-labels and tooltips

Fixes #671

* fix: various a11y refinements

- minify theme-demo-icon.svg
- use & instead of / as it reads better on a screen reader
- prefix classes with `docs-`
- tell screen reader users when a theme has been selected

Fixes #671
alexeagle pushed a commit to alexeagle/material2 that referenced this issue Dec 18, 2024
* build: enable codelyzer and most default Angular CLI TSLint rules

- do some merging of tslint:recommended and our rules

* fix(a11y): fix theme picker keyboard access

enable Codelyzer a11y rules

Relates to angular#671

* fix(component-overview): header does not show up in headings list

Fixes angular#695

* fix(stack-blitz-button): no accessible label and description is not on correct element

Fixes angular#693

* fix(example-viewer): no accessible label on View source button

Fixes angular#693

* fix(component-sidenav): apply aria-current to selected nav items & improve contrast

- use Roboto font instead of system-ui for `docs-nav-content-btn`s
- use a different background color for selected route, in addition to different text color
- increase opacity of `docs-nav-content-btn`s to meet contrast guidelines
- switch to `mat-nav-list` to get the benefits of better contrast and hover/focus styles
  - plus slightly more padding for touch interfaces

Fixes angular#694. Relates to angular#671.

* fix: use header and main tags for more semantic HTML

- improves screen reader support
- footer tags were already properly used

Relates to angular#671.

* fix(component-nav): apply aria-label to navs

- so that they can be differentiated by screen readers

Relates to angular#671.

* fix(component-nav): remove aria-label that duplicates messages

- aria-expanded already covers whether the section can be toggled or not
- the button's text content already covers the accessible name

Relates to angular#671.

* fix(header-link): remove title

- the aria-label is sufficient

Relates to angular#671.

* feat(theme-picker): provide a visual preview of the theme colors via an SVG

* fix(theme-picker,version-picker): add/improve aria-labels and tooltips

Fixes angular#671

* fix: various a11y refinements

- minify theme-demo-icon.svg
- use & instead of / as it reads better on a screen reader
- prefix classes with `docs-`
- tell screen reader users when a theme has been selected

Fixes angular#671
kseamon pushed a commit to kseamon/material2 that referenced this issue Dec 18, 2024
* build: enable codelyzer and most default Angular CLI TSLint rules

- do some merging of tslint:recommended and our rules

* fix(a11y): fix theme picker keyboard access

enable Codelyzer a11y rules

Relates to angular#671

* fix(component-overview): header does not show up in headings list

Fixes angular#695

* fix(stack-blitz-button): no accessible label and description is not on correct element

Fixes angular#693

* fix(example-viewer): no accessible label on View source button

Fixes angular#693

* fix(component-sidenav): apply aria-current to selected nav items & improve contrast

- use Roboto font instead of system-ui for `docs-nav-content-btn`s
- use a different background color for selected route, in addition to different text color
- increase opacity of `docs-nav-content-btn`s to meet contrast guidelines
- switch to `mat-nav-list` to get the benefits of better contrast and hover/focus styles
  - plus slightly more padding for touch interfaces

Fixes angular#694. Relates to angular#671.

* fix: use header and main tags for more semantic HTML

- improves screen reader support
- footer tags were already properly used

Relates to angular#671.

* fix(component-nav): apply aria-label to navs

- so that they can be differentiated by screen readers

Relates to angular#671.

* fix(component-nav): remove aria-label that duplicates messages

- aria-expanded already covers whether the section can be toggled or not
- the button's text content already covers the accessible name

Relates to angular#671.

* fix(header-link): remove title

- the aria-label is sufficient

Relates to angular#671.

* feat(theme-picker): provide a visual preview of the theme colors via an SVG

* fix(theme-picker,version-picker): add/improve aria-labels and tooltips

Fixes angular#671

* fix: various a11y refinements

- minify theme-demo-icon.svg
- use & instead of / as it reads better on a screen reader
- prefix classes with `docs-`
- tell screen reader users when a theme has been selected

Fixes angular#671
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants