Skip to content

fix(material-experimental/mdc-slide-toggle): initial checked and disabled state not reflected visually #17991

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

devversion
Copy link
Member

The initial checked and disabled state of the slide-toggle
is not reflected visually. This is because we sync the disabled
and checked state after the foundation has been created in the
ngAfterViewInit lifecycle hook.

The foundation then tries to set the classes on the MDC switch
element using the adapter. The adapter just updates an object
literal that will be passed through [ngClass] and relies on
Angular to refresh the view.

This won't work in Ivy because marking a component as dirty
from within the ngAfterViewInit lifecycle hook is a noop at the time
of writing. See: FW-1354.

Just using the native element (like we do in other MDC components)
solves this problem and also avoids unnecessary change detections.

…bled state not reflected

The initial `checked` and `disabled` state of the slide-toggle
is not reflected visually. This is because we sync the disabled
and checked state after the foundation has been created in the
`ngAfterViewInit` lifecycle hook.

The foundation then tries to set the classes on the MDC switch
element using the adapter. The adapter just updates an object
literal that will be passed through `[ngClass]` and relies on
Angular to refresh the view.

This won't work in Ivy because marking a component as dirty
from within the `ngAfterViewInit` lifecycle hook is a noop. See: FW-1354.

Just using the native element (like we do in other MDC components)
solves this problem and also avoids unnecessary change detections.
@devversion devversion added the target: patch This PR is targeted for the next patch release label Dec 17, 2019
@devversion devversion requested a review from crisbeto as a code owner December 17, 2019 16:24
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Dec 17, 2019
Copy link
Member

@crisbeto crisbeto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@crisbeto crisbeto added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Dec 17, 2019
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mmalerba mmalerba merged commit e746895 into angular:master Dec 29, 2019
@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jan 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants