Skip to content

ControlValueAccessor for native <select> not working on initial pass #115

@Airblader

Description

@Airblader

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Comp: CoreCore functionality of ngqpPriority: MediumUsers can work without this for now, but this should be fixed soon-ishStatus: Needs TriageWe need to properly tag this issueType: BugSomething that should work doesn'tgood first issueGood for newcomers

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions