Opened 10 years ago
Closed 7 years ago
#9541 closed feature (fixed)
Button: Use control.labels if available
| Reported by: | Scott González | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | 1.12.0 |
| Component: | ui.button | Version: | 1.10.3 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description (last modified by )
http://www.whatwg.org/specs/web-apps/current-work/multipage/forms.html#dom-lfe-labels
This should improve performance where supported.
Change History (4)
comment:1 Changed 10 years ago by
| Status: | new → open |
|---|
comment:2 Changed 10 years ago by
| Description: | modified (diff) |
|---|---|
| Summary: | Button: Use label.control if available → Button: Use control.labels if available |
Turns out we always search in the opposite direction. Updating to use control.labels instead of label.control.
comment:3 Changed 9 years ago by
This is being implemented in the button rewrite: https://github.com/jquery/jquery-ui/pull/1216
comment:4 Changed 7 years ago by
| Milestone: | none → 1.12.0 |
|---|---|
| Resolution: | → fixed |
| Status: | open → closed |
Confirmed fixed in master.
Note: See
TracTickets for help on using
tickets.
We can check the
controlproperty without doing any feature detection. If the result isundefined, then we need to query for the associated control. If it'snull, then there is no associated control.