Validate no variables leak to global
Reported by Joe Gornick | February 21st, 2011 @ 05:21 PM | in Iteration 3
We'll have to validate that after the massive rework commit that none of the variables used for FuseJS leak to the global namespace. If they do, then we will need to make sure they are mapped to the fuse namespace.
Comments and changes to this ticket
-
Joe Gornick March 2nd, 2011 @ 12:00 AM
- Milestone set to “Iteration 1”
- Milestone order changed from “23” to “0”
-
Joe Gornick March 9th, 2011 @ 11:16 AM
- Milestone changed from “Iteration 1” to “Iteration 2”
-
Joe Gornick March 22nd, 2011 @ 10:05 PM
- Milestone changed from “Iteration 2” to “Iteration 3”
- Milestone order changed from “3” to “0”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
JavaScript frameworks share similar features and functionality such as DOM manipulation, event registration, and CSS selector engines. FuseJS attempts to incorporate the strengths of these frameworks into one stable, efficient, and optimized core JavaScript framework.
People watching this ticket
Joe Gornick
John-David Dalton
Referenced by
-
89
Get FuseJS to buildable state
#91
- NEW - Validate no variables leak to
global