If this is going to stick, what about a fallback flag? This way if it breaks code/plugins and the page developer doesnt have enought knowledge to fix the broken code, he can always set the flag to switch the behaviour.
Then in a MANJOR release (2.x) there would be no fallback. IMHO, any API/behaviour breackage in a MINOR release should be heavely documented and justified. Specially because there are many unmantained code out there and non programmers using jQuery. -rsd On Sun, Dec 13, 2009 at 11:06 PM, ajpiano <[email protected]> wrote: > A recent commit - > http://github.com/jquery/jquery/commit/04524287d3e0112deae570ff9247c734833431bb > - changed the behaviour of $() from $(document) to $([]). > > This is a change that I can truly jibe with, and I think the behaviour > makes sense. No one likes having to do $([]) to create an empty jQuery > object. Unfortunately, no change for 1.4 has made me think "will > break a lot of people's code" like this one. For some inane reason, > people (and a lot of tutorials) really started using the $() shortcut, > so the change kind of makes me somewhat uneasy. > > Would love to hear any other perspectives on this. Should the change > stay in and be loudly shouted as a potential 1.4 transition issue, or > rolled back? -- You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en.
