TNG/ngqp

ControlValueAccessor for native <select> not working on initial pass

Airblader opened this issue · 1 comments

What does the bug look like?

When using a native <select> and emptyOn, the initial sync from the route does not work correctly. It seems like in the ControlValueAccessor's writeValue everything is working as it should, but somehow the option does not appear selected.

Wrapping the setProperty call into a Promise.resolve().then() fixes the issue, but of course this is a last straw kind of thing.

We should check if our implementation deviates from others in this instance.

It would also be good to check if this issue can be reproduced with Angular Forms.