Side navigation
#14076 closed feature (wontfix)
Opened June 27, 2013 02:56AM UTC
Closed September 10, 2013 04:42PM UTC
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.
Attachments (0)
Change History (2)
Changed June 27, 2013 02:59AM UTC by comment:1
component: | unfiled → core |
---|---|
milestone: | None → 1.11/2.1 |
owner: | → timmywil |
priority: | undecided → high |
status: | new → assigned |
Changed September 10, 2013 04:42PM UTC by comment:2
resolution: | → wontfix |
---|---|
status: | assigned → closed |
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().