Opened 10 years ago
Closed 9 years ago
#14076 closed feature (wontfix)
Use AMD module config to avoid setting jQuery global
Reported by: | timmywil | Owned by: | timmywil |
---|---|---|---|
Priority: | high | Milestone: | 1.11/2.1 |
Component: | core | Version: | 1.10.1 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
See jrburke's comment on avoiding exporting globals:
https://github.com/jquery/jquery/pull/557#issuecomment-19143292
This is something we could add without changing any default behavior.
Change History (2)
comment:1 Changed 10 years ago by
Component: | unfiled → core |
---|---|
Milestone: | None → 1.11/2.1 |
Owner: | set to timmywil |
Priority: | undecided → high |
Status: | new → assigned |
comment:2 Changed 9 years ago by
Resolution: | → wontfix |
---|---|
Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
After some consideration, I don't think we're going to add this. Exposing the global is not required with custom builds, noConflict config doesn't seem to get a lot of usage, and we still have jQuery.noConflict().