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

[Question]: will this be the official repo for Angular 2 Material? #1

Closed
rolandjitsu opened this issue Jan 8, 2016 · 6 comments
Closed

Comments

@rolandjitsu
Copy link

No description provided.

@zoechi
Copy link

zoechi commented Jan 8, 2016

I assume this one https://github.com/angular/material2

@rolandjitsu
Copy link
Author

Obviously yes, it is the repo the issue is opened on :)

@zoechi
Copy link

zoechi commented Jan 8, 2016

Right :D

@jelbourn
Copy link
Member

jelbourn commented Jan 8, 2016

Yes.

@jelbourn jelbourn closed this as completed Jan 8, 2016
@RainingNight
Copy link

Nice !

mmalerba referenced this issue in mmalerba/components Nov 30, 2016
mmalerba referenced this issue in mmalerba/components Nov 30, 2016
mmalerba referenced this issue in mmalerba/components Dec 1, 2016
mmalerba referenced this issue in mmalerba/components Dec 5, 2016
mmalerba referenced this issue in mmalerba/components Dec 6, 2016
mmalerba referenced this issue in mmalerba/components Dec 7, 2016
mmalerba referenced this issue in mmalerba/components Dec 9, 2016
mmalerba added a commit that referenced this issue Dec 9, 2016
…#2052)

* created md-input-wrapper and removed useless inputs

* added demo

* remove ControlValueAccessor and start migrating input

* finished converting most input attrs

* typescript fixed, css needs work

* removed duplicate directives.

* fix scss

* set up demo area

* Fix disabled state

* fixed some small bugs and converted more of demo

* demo card #1 converted

* finished converting demo

* subscribe to ngModel changes

* updated other demos to use new input

* undo accidental changes to other inputs

* working through tests

* fixed all tests

* fixed lint issues

* fix firefox type=date issue

* try removing ie11 checks, see if we need them

* added md-input back to baseline demo

* started md-input directive

* more refactoring

* fixed demos, tests still broken

* remove useless imports

* fix tests

* fix tests for ff & ie

* move input feature detection into service

* addressed some comments

* s/input-wrapper/input-container

* s/NgModel/NgControl

* remove FeatureDetector

* s/MdPlatformModule/PlatformModule

* Remove some problematic privates and add mat- versions of everything

* fix import
@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 4, 2019
zarend referenced this issue in zarend/components Feb 2, 2022
…Down

Do not merge this pls. Debugging issue angular#2430.

There seems to be two issues

1. The screenreader focus doesn't not match the browser focus
2. the aria-live region is interfering with reading the focused element

Adds a timeout to fix #1, and removes the aria-live region to fix angular#2. This is not the final solution, requires more investigation...

Relates to angular#24330
zarend referenced this issue in zarend/components Feb 10, 2022
…Down

Do not merge this pls. Debugging issue angular#2430.

There seems to be two issues

1. The screenreader focus doesn't not match the browser focus
2. the aria-live region is interfering with reading the focused element

Adds a timeout to fix #1, and removes the aria-live region to fix angular#2. This is not the final solution, requires more investigation...

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

Successfully merging a pull request may close this issue.

4 participants