Opened 6 years ago
Closed 6 years ago
#13801 closed feature (fixed)
Deprecate context property
| Reported by: | gibson042 | Owned by: | |
|---|---|---|---|
| Priority: | low | Milestone: | 1.10 |
| Component: | core | Version: | 1.9.1 |
| Keywords: | 1.10-discuss 1.11-discuss | Cc: | |
| Blocked by: | Blocking: | #14341 |
Description
#9469 made a good (and ultimately successful) case for deprecating the selector property because of its needlessness and inherent unreliability. We should do the same with its sibling property context for exactly the same reasons.
Cf. https://github.com/jquery/jquery/pull/1249, closed because context is still publicly documented.
Change History (14)
comment:1 Changed 6 years ago by
comment:2 Changed 6 years ago by
| Component: | unfiled → core |
|---|---|
| Keywords: | 1.10-discuss added |
| Priority: | undecided → low |
| Status: | new → open |
+1, we always use ownerDocument anyway.
comment:4 Changed 6 years ago by
+1, Good with the deprecation/removal but not the time frame. 2.0 has shipped, and 1.10 should parallel it. Do you mean 2.1/1.11 here?
comment:5 Changed 6 years ago by
2.1/1.11 is the most realistic. It'd be nice to get this sooner, but 2.0 has already left the barn.
comment:6 Changed 6 years ago by
| Milestone: | None → 1.11/2.1 |
|---|
comment:7 Changed 6 years ago by
| Keywords: | 1.11-discuss added; 1.10-discuss removed |
|---|
comment:8 Changed 6 years ago by
| Keywords: | 1.10-discuss added |
|---|
I think this was miscommunicated. Let's deprecate it now (1.10) and remove the code when we can.
comment:9 Changed 6 years ago by
| Milestone: | 1.11/2.1 → 1.10 |
|---|
comment:12 Changed 6 years ago by
We have a race condition here. ;) The pull request is almost ready to merge but I need the URL to the blog post about the 1.10 release so we'll wait for the release with merging that. :)
comment:13 Changed 6 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | open → closed |
comment:14 Changed 4 years ago by
| Blocking: | 14341 added |
|---|
+1