You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 7, 2020. It is now read-only.
Describe the bug
The mdc-list and the underlaying mdc-list-items getting automatic a id. Even when the id is manually provided.
The id is in this schema <componet-name>-<n> - so if we have a two lists like this ...
Then the id's a automatic set somewhere. It doesn't matter if we set a id manually (with one variant of <mdc-list-item id="test" [id]="'test'" [attr.id]="'test'" ...), there is always the generated id.
To Reproduce
Steps to reproduce the behavior:
Setup a list and inspect the id's.
Expected behavior
If a id was set manually, then it never gets overwritten.
Otherwise it is really hard to write test-cases for e2e in a big project, when the id`s "randomly" changed.
Screenshots
It seems, that the behaviour is also on the examples.
What Angular MDC version are you using? 5.1.1
What OS are you using?: Linux and Windows
What browser(s) is this bug affecting?: Chrome and Firefox
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
The
mdc-list
and the underlayingmdc-list-items
getting automatic a id. Even when the id is manually provided.The id is in this schema
<componet-name>-<n>
- so if we have a two lists like this ...Then the id's a automatic set somewhere. It doesn't matter if we set a id manually (with one variant of
<mdc-list-item id="test" [id]="'test'" [attr.id]="'test'" ...
), there is always the generated id.To Reproduce
Steps to reproduce the behavior:
Expected behavior
If a id was set manually, then it never gets overwritten.
Otherwise it is really hard to write test-cases for e2e in a big project, when the id`s "randomly" changed.
Screenshots

It seems, that the behaviour is also on the examples.
What Angular MDC version are you using? 5.1.1
What OS are you using?: Linux and Windows
What browser(s) is this bug affecting?: Chrome and Firefox
The text was updated successfully, but these errors were encountered: