Skip to content
This repository has been archived by the owner on Apr 13, 2022. It is now read-only.

perf(ngModel): avoid setting classes multiple times for parse / validator errors #16357

Open
1 of 3 tasks
Narretz opened this issue Dec 4, 2017 · 0 comments
Open
1 of 3 tasks

perf(ngModel): avoid setting classes multiple times for parse / validator errors #16357

Narretz opened this issue Dec 4, 2017 · 0 comments
Assignees
@jbedard
Labels
component: forms type: perf
Milestone
1.8.x - won't fix

Comments

@Narretz
Copy link
Contributor

Narretz commented Dec 4, 2017

I'm submitting a ...

  • bug report
  • feature request
  • other

Current behavior:

See #14292 (comment)

Expected / new behavior:

Minimal reproduction of the problem with instructions:

AngularJS version: 1.x.y

Browser: [all | Chrome XX | Firefox XX | Edge XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Anything else:
@Narretz Narretz added this to the Backlog milestone Dec 4, 2017
@Narretz Narretz changed the title perf(ngModel): avoid setting classes multiple types for parse / validator errors perf(ngModel): avoid setting classes multiple times for parse / validator errors Dec 4, 2017
@jbedard jbedard self-assigned this May 3, 2018
@jbedard jbedard modified the milestones: Backlog, 1.7.x - won't fix Jan 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jbedard jbedard

Labels
component: forms type: perf
Projects
None yet
Milestone
1.8.x - won't fix
Development

No branches or pull requests
2 participants
@jbedard @Narretz