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
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.
![image](https://user-images.githubusercontent.com/15613049/82235467-08e79d00-9933-11ea-8ce1-234fde206b46.png)
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