Skip to content
This repository was archived by the owner on Sep 5, 2024. It is now read-only.

checkbox: clicking links in labels also toggles the value #10823

Open
nikclayton opened this issue Jul 31, 2017 · 1 comment
Open

checkbox: clicking links in labels also toggles the value #10823

nikclayton opened this issue Jul 31, 2017 · 1 comment
Assignees
Labels
for: internal contributor The team will address this issue and community PRs are not requested. g3: reported The issue was reported by an internal or external product team. needs: investigation The cause of this issue is not well understood and needs to be investigated by the team or community P3: important Important issues that really should be fixed when possible. type: bug
Milestone

Comments

@nikclayton
Copy link

nikclayton commented Jul 31, 2017

Actual Behavior:

  • What is the issue? *
    If an md-checkbox has a text or a label that contains a link, clicking the link (either with _target="blank" to open in a new tab, or Ctrl-click) also toggles the checkbox.
  • What is the expected behavior?
    Not toggle the checkbox. This is the behavior of the native <input type="checkbox">.

CodePen (or steps to reproduce the issue): *

AngularJS Versions: *

  • AngularJS Version: 1.6.4
  • AngularJS Material Version: 1.1.4

Additional Information:

  • Browser Type: * Chrome
  • Browser Version: * 59.0.3071.115 (Official Build) (64-bit)
  • OS: * Ubuntu 14.04
  • Stack Traces: N/A
@Splaktar Splaktar added the g3: reported The issue was reported by an internal or external product team. label Jan 16, 2019
@Splaktar Splaktar self-assigned this Jan 16, 2019
@Splaktar Splaktar added this to the 1.1.13 milestone Jan 16, 2019
@Splaktar Splaktar changed the title Clicking links in checkbox labels also clicks the checkbox. <input type="checkbox"> does not do this. checkbox: clicking links in labels also toggles the value Jan 22, 2019
@Splaktar Splaktar added type: bug P3: important Important issues that really should be fixed when possible. needs: investigation The cause of this issue is not well understood and needs to be investigated by the team or community labels Jan 22, 2019
@Splaktar
Copy link
Member

Splaktar commented Jan 22, 2019

This is related to #11134, which can't be fixed until 1.2.0. I need to investigate whether this can be fixed prior to 1.2.0.

@Splaktar Splaktar added for: internal contributor The team will address this issue and community PRs are not requested. for: external contributor labels Jan 22, 2019
@Splaktar Splaktar modified the milestones: 1.1.13, 1.1.14 Feb 10, 2019
@Splaktar Splaktar modified the milestones: 1.1.14, g3: sync Feb 15, 2019
@Splaktar Splaktar modified the milestones: g3: sync, 1.1.23, 1.2.1 Apr 30, 2020
@Splaktar Splaktar modified the milestones: 1.2.1, 1.2.2 Sep 14, 2020
@Splaktar Splaktar modified the milestones: 1.2.2, - Backlog Dec 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
for: internal contributor The team will address this issue and community PRs are not requested. g3: reported The issue was reported by an internal or external product team. needs: investigation The cause of this issue is not well understood and needs to be investigated by the team or community P3: important Important issues that really should be fixed when possible. type: bug
Projects
None yet
Development

No branches or pull requests

2 participants