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 }}
Repository navigation
bug(form): NgForm should not use camelCase in element selector #23678
[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
[ ] Other... Please describe:
What is the motivation / use case for changing the behavior?
It completely break the design consistency.
Also using (non-native) element selector is useful for nested forms as in AngularJS, should not be removed.
Angular version: 2.0.0-alpha.52 ~ 6.0.0-rc.6
Browser:
- [ ] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
For Tooling issues:
- Node version: XX
- Platform:
Others:
changed the title [-]bug(form): NgForm should not use camelCase in element selecter[/-][+]bug(form): NgForm should not use camelCase in element selector[/+]on May 3, 2018
ouch. I'm surprised we haven't noticed this before. you are right, we should fix this by deprecating the old selector and introducing the correct one + figuring out the migration path.
Activity
[-]bug(form): NgForm should not use camelCase in element selecter[/-][+]bug(form): NgForm should not use camelCase in element selector[/+]IgorMinar commentedon May 3, 2018
ouch. I'm surprised we haven't noticed this before. you are right, we should fix this by deprecating the old selector and introducing the correct one + figuring out the migration path.
angular-automatic-lock-bot commentedon Sep 13, 2019
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.