Fixed Events
Can we use a different property to track fixed events or make the expando public? It would be really useful to be able to detect if an event is fixed outside of core, or be able to remove the flag to allow the event to be fixed again. The problem I'm running into is I have an event that has already been fixed, like mousemove. I want to create a new event, like drag, from the mousemove event. I can't use $.event.fix(event) because the first thing is does is check if the event has already been fixed
Handling forms with overwritten methods (submit/reset)
Brandon, here is a sample of the trick used to overcome these "form" annoyances, I will gladly open an enhancement ticket if deemed interesting to have in jQuery. I will first let it here for comment reviews. Some point: - I used DOM0 event "onmouseup" to avoid including cross-browser code adaption, and because they fire first - nothing useful in this snippet alone, it is a tentative fix for some bug due to badly chosen element names in forms - the interesting objective is just be able to restore
getJSON get wrong content but no error returned
for picasa, if enter a wrong userid in the link, the page will print a string "Unable to find user with email xxx@gmail.com" instead of a json object. Is there anyway to detect the return string is in wrong format? I tried ajaxComplete,ajaxError,ajaxStop,ajaxSuccess, none of them triggered if the remote file is in wrong format. And if I put a button in the page to trigger ajax, the first time ajaxSend is triggered, but from the second time ajaxSend not working. I am using jquery-1.3.1.min.js. Appreciate
20%+ faster replaceWith?
Hey all, Looking at the new source code for 1.3, I was wondering why jQuery doesn't take advantage of the native replaceChild method in the W3C core. Currently, jQuery implements replaceWith using append and remove, but since replaceChild is well supported[1] across browsers, it seems like a safe place to optimize performance, since it reduces two in-place DOM operations with one. So I replaced this on line 487 in 1.3: replaceWith: function( value ) { return this.after( value ).remove(); }, with
env.js's XMLHttpRequest won't add message content to outgoing HTTP POST [fix included]
While using http://dev.jquery.com/browser/trunk/jquery/build/runtest/env.js for some unit tests, I noticed that outgoing HTTP POST requests could not have body content. This prevents env.js from begin useful for unit tests against APIs that use the POST body to contain JSON-RPC information. Specifically, look at function makeRequest() beginning on line 584 in SVN trunk (link above). You'll see near line 590 that the file: PUT case uses a FileWriter to output variable 'data' to the file. Now look
Error in Firefox mac
<br clear="all">Hi, I have created plugin that extends the jQuery.browser extension, but it is not working only on firefox mac(in safari it is ok), not executing the plugin as it should.(it doesn't detect any of the browser plugins) Could this be a browser bug, or an i missing something? Here is the plugin demo page:<a href="http://jqplugins.appspot.com/jqplugin">http://jqplugins.appspot.com/jqplugin</a> Thanks -- Leonardo Rosseti, Web Developer / Desenvolvedor Web Profile / Perfil: <a href="http://www.linkedin.com/in/leoros">http://www.linkedin.com/in/leoros</a>
quickExpr invalid w3c ID/NAME regexp
Hi, I'm using jQuery in a BEA 8 Portal solution (yeah - I know its quite old), but jQuery fails to handle the rather weird looking ID's generated by the BEA Portal. At first I thought it was a bug in the portal software, but it turns out its both BEA and jQuery which fails. Current jQuery (1.3.1) quickExp : /^[^<]*(<(.|\s)+>)[^>]*$|^#([\w-]+) $/, But as stated by the W3C docs: http://www.w3.org/TR/REC-html40/types.html#type-name <quote> ID and NAME tokens must begin with a letter ([A-Za-z]) and may
Registration Page
Hello, Just a quick note that I am trying to register with the dev site of jQuery, but the registration page is non-existent reporting: ==== How to Reproduce ==== While doing a GET operation on `/register`, Trac issued an internal error. ==== System Information ==== || '''Trac''' || `0.11dev-r5354` || || '''Python''' || `2.3.4 (#1, Oct 11 2006, 06:18:43) ` [[br]] `[GCC 3.4.6 20060404 (Red Hat 3.4.6-3)]` || || '''setuptools''' || `0.6c5` || || '''MySQL''' || `server: "5.0.27-log", client: "5.0.27",
bug with animating height / width change in webkit browsers - div loses overflow property
This bug with jquery releases 1.2.6, 1.3, and 1.3.1 I have a div with overflow set to auto. If I resize that div with .animate, the overflow setting will completely disappear in safari & chrome. For example, if you have a 200px tall div and animate it down to 150px, anything that was contained by the overflow:auto will come spilling out the bottom. Same thing happens to :scroll and :hidden settings. Instant resizing using .css doesn't cause any problems. Using the element inspect confirms that the
jquery 1.2.6 focus problem?
Hey all, Our project is using 1.2.6, but we seem to have an issue with calling: $('#some-textbox-id').focus(); The element focuses properly, but it seems like the next time you press the tab key the focus completely disappears and you have to hit it several times to get it back into the flow of the document rather then going to the next focusable element in the DOM. Is this a bug or am I missing something? If you click back onto the document and focus on something it will resume the natural behavior.
Event delegation
jQuery developers, I've heard that event delegation is being added to many of the big JS libraries, including jQuery. It has been a major component of JavaScriptMVC. For JavaScriptMVC's next version, I'm considering using jQuery by default and replacing any redundant functionality with jQuery or its plugins. For this to happen, I'd like to help with JavaScriptMVC's code if necessary. How far along is this effort? Have you already figured out the special edge cases -> submit/change in IE, change in
Live events and triggerHandler()
One question: Why triggerHandler() doesnt trigger live events? Is this behaviour expected? Is it a bug? Example here: http://reinaldojunior.net/publico/test-bug-triggerHandler.html Instructions: 1) Click "Insert Row" to insert rows =D 2) Click inside the input and look at your Firebug console 3) Click inside the TD but outside the input and look at your Firebug console If you mark "Use triggerHandler" the TD click event will use triggerHandler.
.live() not binding events consistently
Hi All, I'm using .live() to bind events to forms returned by AJAX requests. $('#TB_ajaxContent form').live("submit",function(){ alert('test'); $(this).ajaxSubmit(options); return false; }); This is used with thickbox and jquery.form to allow each returned form to be used to make AJAX POSTs. It all seemed to be working fine but I've found that it doesn't seem to work on all machines. I've tested it using Firefox 3.0.5 (Mac and Windows) and Safari 3.2 (Windows) and it works
Selecting JUST visible elements (without getting the elements that are inside INvisible elements)
The concept is simple: to find the elements that are visible at the screen. But by using the :visible selector, it verify only the element itself, so if a parent element is hidden, the child is still considered as visible. Here's an example markup: <div style="display:none;"><span>TEST</span></div> If we use this selector: $("div:visible"); It will find nothing because the div is not being shown. But, if we use this: $("div span:visible"); It finds the span even when the tag tag is inside a hidden
jQuery test case app
Partially out of personal laziness in manually creating test cases with the same boilerplate over and over again, I made a really simple app that'll help that process along. http://jquery.nodnod.net/ For example, here's a sample case: http://jquery.nodnod.net/cases/7 The dropdowns allow easy switching between the three most recent versions of jQuery -- and more can be added pretty easily. The source code for jquerytester (built with django) is open and available at: http://github.com/dz/jquerytester/
Problem with selectors in Safari
I encountered a really weird problem in Safari in the 1.3+ releases of jQuery. The case: http://jquery.nodnod.net/cases/37 (permanent http://friedcellcollective.net/js/Cases/select-active.txt) When you click a node it is marked as selected and all it's parent nodes are marked as active. When you deselect, it iterates through the active parent nodes, checking if they have any selected descendants - if they do, they're left active, otherwise their active state is removed. It works in 1.2.6, but doesn't
JQuery
My template JSP has the following JQuery code in head secion <script language="javascript" type="text/javascript"> jQuery(document).ready(function($) { // bind form using ajaxForm $('.queueForms').ajaxForm(); }); </script> My calling code is in another JSP which is included in the template code above: <form class="queueForms" id="htmlForm" action="/MarketFrontend/ soDetailsQueueNote.action" method="post"> Message: <input type="text"
Expected behavior with XmlHttpRequest.abort() and ajaxStop event
Hi, I have a question related to a bug in Tabs: http://ui.jquery.com/bugs/ticket/3903 So I'm using the XmlHttpRequest abort method to cancel a running request if another tab is being selected. In that case no ajaxStop event is fired for the former (obsolete) request. I am now wondering what the expected behavior is here. Would it be expected to fire ajaxStop for such a canceled XHR request? In that case it wouldn't be a bug in tabs but in jQuery itself. If the current behavior is as expected, the
.index() enhancement
It would be useful to be able to use the .index() method to find the index of the current element in a given set, rather than the current implementation (searching the current set for a given element), which forces the developer to do gyrations in order to find out a simple piece of info. For instance $("#sometable th img").click(function() { //find out index of img's parent <th> in its own <tr> var $th = $(this).parent(); //now we have a few not so great choices //1. var index = $("#sometable thead
Given two jQuery objects a and b, find whether b is within a
See <a href="http://groups.google.com/group/jquery-en/browse_thread/thread/9efd1af2e2076eb9">http://groups.google.com/group/jquery-en/browse_thread/thread/9efd1af2e2076eb9</a> Is this a bug? test("Given two jQuery objects a and b, find whether b is within a. Test 1: b not within a", function() { //b is not within a //expect 0 var a = jQuery('<div id="a"></div>'); var b = jQuery('<div id="b"></div>'); equals( jQuery(b[0], a[0]).length, 0 ); equals( a.find(b[0]).length, 0 );
I'm confused with [attr!=value]
In the docs it shows that [attr!=value] Matches elements that have the specified attribute but not with a certain value. (http://docs.jquery.com/Selectors/attributeNotEqual#attributevalue) But in the recent changes in jQuery 1.3.1,it seems to revert. (http://dev.jquery.com/changeset/6149) So I just wonder whether it will change again? thx~
IE 6 & 7 reports incorrect CSS opacity values in jQuery 1.3.1
I've found that in IE 6 & 7, jQuery 1.3.1 seems to return incorrect CSS opacity values for elements that have `filter: alpha(opacity=N);` applied in a stylesheet. However, elements with their opacity level set with a `style=""` attribute, return the correct number. Additionally elements with opacity set to `0` seem to return `1` in IE 6 & 7... Here's a test case: http://mar.eplica.is/ie-opacity-bug-demo.html And another test using my patched version of jQuery 1.3.1: http://mar.eplica.is/ie-opacity-fixed.html
1.3 - Removal of passing JS Objects to jQuery()?
Ello, In 1.2.6 I can do var data = {}; data.x = { a: [], b: [] } data.x.a.push({ name: "foo", num: 0 }); data.x.a.push({ name: "foo2", num: 0 }); $(data.x.a).filter('[name="foo"]') And I get the expected object { name: "foo", num: 0 } However, in 1.3 I now get an empty jQuery object (length=0). Has this (undocumented) functionality been removed due to Sizzle? Are there any plans to bring it back in a future release? I *need* to use this for a large project I've been working on, but we want to upgrade
Can't bind event to <img> with a title tag
This works: nextTag = $("<img src='image.gif' alt='value' />"); nextTag.bind('click', clickMe); This Fails: nextTag = $("<img src='image.gif' title='value' />"); nextTag.bind('click', clickMe); with a no such method error. Should I submit this to the Bug Tracker?
Is this a Bug?
When i try to reference a textarea in the parent window, for the first time it will return 'undefined', and will return '[object HTMLTextAreaElement]' thereafter. This happens to both Firefox 3.0.5 and IE 7.0.5730.13 under XP SP3. Here are the two html files; ---------------------------------------------------------------------------------------------------------------------------------- parent.html: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
IE Memory Leak in ajax getScript() calls
Hello, I've found and fixed a small memory leak in the jQuery 1.2.6 codebase that pertains to the getScript ajax methods. (around line 2670 in jQuery 1.2.6) the new code is as follows - I added script.onload = script.onreadystatechange = null; right before the head.removeChild( script ); call to help IE collect its garbage. // Attach handlers for all browsers script.onload = script.onreadystatechange = function(){ if ( !done && (!this.readyState || this.readyState == "loaded" || this.readyState
.live() and selector context operation...?
I know that functionally the following two are equivalent: $("table .qty").live("click", function(e){ alert("hello"); }); $tbls = $("table"); $(".qty", $tbls).live("click", function(e){ alert("hello"); }); what i'd like to find out is if the $live delegation works the same in both cases. From thinking about it, the second case would delegate less efficiently, because there is no full selector provided. the problem is that i have a function like this: function tblCalcs($tbls) { $(".qty", $tbls).live("click",
Bug? Newly created elements have a parent <div>
`$('<p />').parent()` returns the <div> wrapper for the innerHTML injection when creating the paragraph element. This makes it impossible to distinguish between a newly created element and an element that is intentionally wrapped in a <div>. Smells like a bug. Can this be fixed without breaking lots of other functionality? possible fix would be to add something like: while (div.lastChild) { div.removeChild(div.lastChild); } *after* the line elem = jQuery.makeArray( div.childNodes ); within `$.clean()`.
position() question
You know that when an element has position absolute, it does not necessary mean that its position is from top and left of the page. For example, if I have a situation like this one: <div style="position:relative;top:100px;left:100px;"> This text is not visible <div id="nested" style="position:absolute;top:0px;left:0px;height:100px;background-color:#FFF;"> Hello relatively absolute position </div> </div> The nested div with absolute position will be positioned at the top left
Roadmap 1.4 or 2.0?
Hi, I was just curious, is there any roadmap or list of feature requests for the next major release after jquery 1.3? Greets, Abdul
selector regressions in 1.3rc2
hi, just tested the 1.3rc2, and it seems the attribute selector doesn't work when selecting the anchor links: $('a[href^=#]') returns zero objects. another very weird bug: $('*').size() shows zero results... tested on FF 3.0.5 and Safari 3.2.1 I haven't filled a bug report yet, thought maybe you're already on it.
passing params to .live
Are we going to be able to pass parameters to the callback live function like we can with event callback functions? function foo(e) { alert(e.data.bar); } $function(){ //This works right now: $('a').bind('click', {bar:'fubar'}, foo); //This doesn't: $('a').live('click', {bar:'fubar'}, foo); }
immunity from Object.prototype modifications
I know there are plans to be immune from Object.prototype modifications. What release is this immunity expected to land in? Until we get there, how should tickets related to this be handled (see <a href="http://dev.jquery.com/ticket/3763#comment:3">http://dev.jquery.com/ticket/3763#comment:3</a>)?
new whitehouse.gov uses jQuery
they're still at v1.2.6 though...tsk tsk tsk.
jQuery under a different API
Has there been any thought, discussion, or interest in providing jQuery as a backend, or being able to provide another library as another API to jQuery. jQuery is quite mature (even though a bug I couldn't track down forced us to discard use of it at work), but one of the things that has irked me repeatedly is small commonly used parts of the API. Namely show/ hide, toggle, end, and sometimes I've thought the bind/live... separation could be done better. Of course even if the API could be done a
sizzle well hung on descendents of non existent element
trying to move to 1.3, on page load I do something like $('div.thiselementisnotavailableyet>ul>li').each(...) and sizzle is well hung. I can bypass this error by making the following change test for array end in the TAG function of the preFilter element of Sizzle.selectors line 1774 of jquery-1.3.js : for ( var i=0; !curLoop[i]; i++ ){ if (i==curLoop.length) return false; } I am sorry that I haven't delved deeper to fully understand what's happening, but I have other responsibilities, and I suspect
Jquery + Firebug (suspended) weirdness
I really hate not having a thorough test-case, but I really am mystified by this. I'm running Firefox 3.0.5 with firebug. This page (test case): http://www.partyark.co.uk/html/jqtest.html has a super-minimal, unstyled jQuery + jQuery UI tab. The page doesn't do anything unsurprising - until you 'suspend' firebug (right-click the little bug at the bottom and 'suspend'). Reloading the page will cause jQuery to reload parts of the page every few seconds (check your HTTP headers), cause the CPU to spike
$.ajax, jQuery 1.3, not working with url containing fragment identifier in IE
All, I'd like to confirm if this is a bug - if you have a url containing a fragment identifier like "test.html#test" then using $.ajax the request will not successfully load in IE (tested in IE7, e.g. IE8 in IE7 mode, standards mode). $.ajax({ url: "test.html#test" }); I ran into that issue with Tabs yesterday. Am I correct? --Klaus
UI Tabs - Automatically initialize inline links to activate tabs
Hi, The following line, when added to the UI Tabs init() method, just prior to the event handler binding, causes all links with href attributes equivalent to those in tab nav to become tied to the tab nav automatically. <span style="font-family: courier new,monospace;">this.$lis.each(function(){var tab=$('a[href]',this);$('a[href='+tab.attr('href')+']').each(function(){if(this!=tab){$(this).click(function(){tab.trigger(o.event+'.tabs');/*this should probably scroll to the top of the appropriate tab
Bug in selector ':gt' in jQuery 1.3
It's easier to show a test case: 1) Open <a href="http://reinaldojunior.net/publico/test-bug-gt.html">http://reinaldojunior.net/publico/test-bug-gt.html</a> 2) Look the Firebug console. The problem: In jQuery 1.2.6 $('.testing tr:gt(0)') matches 10 elements But in jQuery 1.3 $('.testing tr:gt(0)') matches 20 elements <div class="testing"> <span class="testing"><table>...</table></span></div> -- Reinaldo de Souza "JuniorZ" <a href="http://reinaldojunior.net">http://reinaldojunior.net</a> -- Non ducor,
Next Page