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

slide-toggle doesn't work as expected with EdgeBrowser and IE11 #8391

Closed
wuchtig opened this issue Nov 12, 2017 · 1 comment · Fixed by #8421
Closed

slide-toggle doesn't work as expected with EdgeBrowser and IE11 #8391

wuchtig opened this issue Nov 12, 2017 · 1 comment · Fixed by #8421
Assignees

Comments

@wuchtig
Copy link

wuchtig commented Nov 12, 2017

Bug, feature request, or proposal:

Slide-toggle doesn't work as expected with EdgeBrowser and IE11.
Click thumb works.
Drag thumb works but it flips back

What is the expected behavior?

Slide-toggle should work with drag thumb

What is the current behavior?

slidetoggle

What are the steps to reproduce?

Look at Material Demo Site or the Plunker

Which versions of Angular, Material, OS, TypeScript, browsers are affected?

MSEdge: 41.16299.15.0
Material: 5.0.0-rc0-3ca801a

@devversion devversion self-assigned this Nov 13, 2017
devversion added a commit to devversion/material2 that referenced this issue Nov 13, 2017
Some browsers like Edge or IE11 emit `click` events differently than other browsers like Chrome. For example does Edge still emit a `click` event if the pointer drags something around and is being released over the `<label>` element. This doesn't happen on Chrome.

Right now this means that the new checked state from the drag is being reverted by the `click` event that then causes a `change` event on the underlying input element. To ensure that the behavior is the same across all supported browsers, the checked state from the `click` event is being ignored while dragging.

Fixes angular#8391
jelbourn pushed a commit that referenced this issue Nov 18, 2017
Some browsers like Edge or IE11 emit `click` events differently than other browsers like Chrome. For example does Edge still emit a `click` event if the pointer drags something around and is being released over the `<label>` element. This doesn't happen on Chrome.

Right now this means that the new checked state from the drag is being reverted by the `click` event that then causes a `change` event on the underlying input element. To ensure that the behavior is the same across all supported browsers, the checked state from the `click` event is being ignored while dragging.

Fixes #8391
jelbourn pushed a commit that referenced this issue Nov 20, 2017
Some browsers like Edge or IE11 emit `click` events differently than other browsers like Chrome. For example does Edge still emit a `click` event if the pointer drags something around and is being released over the `<label>` element. This doesn't happen on Chrome.

Right now this means that the new checked state from the drag is being reverted by the `click` event that then causes a `change` event on the underlying input element. To ensure that the behavior is the same across all supported browsers, the checked state from the `click` event is being ignored while dragging.

Fixes #8391
@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 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants