Skip to content
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

mdCheckbox: Styles not applied correctly when not explicitly given a [checked] value #183

Closed
traviskaufman opened this issue Mar 16, 2016 · 1 comment
Assignees
Labels
P2 The issue is important to a large percentage of users, with a workaround
Milestone

Comments

@traviskaufman
Copy link
Contributor

When a checkbox is not explicitly given a [checked] input value, the first time it's clicked it simply fades in instead of drawing itself in. This is likely an issue of the svg stroke-dashoffset not being applied correctly within the unchecked state.

@traviskaufman traviskaufman self-assigned this Mar 16, 2016
@jelbourn jelbourn added this to the alpha.2 milestone Mar 16, 2016
@jelbourn jelbourn added the P2 The issue is important to a large percentage of users, with a workaround label Mar 16, 2016
traviskaufman added a commit to traviskaufman/material2 that referenced this issue Mar 24, 2016
This commit fixes a bug where the initial `unchecked -> checked`
animation wasn't firing correctly when the checkbox was interacted with
from its initial state (e.g. when `[checked]` or `[(ngModel)]` isn't
bound to the component).

Fixes angular#183.
andrewseguin pushed a commit to andrewseguin/components that referenced this issue Oct 15, 2018
@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 Sep 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P2 The issue is important to a large percentage of users, with a workaround
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants