At the time you create your ObjectMap, do the DOM elements you're trying to
reference already exist?
If your ObjectMap definition is earlier in the HTML output than the DOM
elements themselves, then they won't exist yet. In your test code, if you
look at o.length, I'll bet it's zero - which means
It appears to be a problem with how the selector expression passed to
not() is parsed (so the problem is not with the wildcard selector).
I've found that this works:
jQuery('#ap *').not('code, #mark')
but this doesn't:
jQuery('#ap *').not('#mark, code')
Note the order (ID, TAG) doesn't work,
Reposted from jquery-en at the request of Dave Methvin:
Hey guys, I'm finding it really hard to use Trac to keep tabs on
jQuery development and the bugs I've filed. There are just a couple of
weird things about jQuery's instance of Trac that make things hard:
* I don't get emailed when tickets a
Hello All,
I'm trying to create a jQuery map/array of all controls on an ASP.net
page for easier client runtime access. I output the following to the
page:
var ObjectMap = {
ctl00: $("#ctl00_DefaultContent_ctl00"),
chkEmployee: $("#ctl00_DefaultCon
On Dec 23, 2008, at 5:21 AM, pixeline wrote:
> $('*', allItems).not('p, a,form').show();
>
> triggers this error in firebug:
> Error:
> match[3] is undefined
> jquery-1.3b1.js
> Line 1812
>
> testcase here: http://pixeline.be/experiments/jquerybeta/test1.html
>
>
> it seems related to the use of t
Yes, but you're still encouraged to go the same way and replace your
usage of jQuery.browser with feature detection.
Jörn
On Tue, Dec 23, 2008 at 7:28 PM, Ricardo Tomasi wrote:
>
> I thought browser detection wasn't going to be used in jQuery's core
> anymore, but jQuery.browser would remain for
I thought browser detection wasn't going to be used in jQuery's core
anymore, but jQuery.browser would remain for end-users, am I right?
- ricardo
On Dec 23, 2:44 am, Shade wrote:
> Just a question/thought on the complete deprecation of
> jQuery.browser I know the new model is to go toward
I've got the same document.write problem.
I think that at a slow pace we shoud force the ad providers to stop
using document.write and start ising json or jsonp.
jsonp make for a perfect cross domain call. Ok it's insecure, but
document.write brings the same security problems and we already deal
Got your point, Kurt, thanks for the tip! Didn't realize this at the time I
wrote my answer...
Diogo
On Mon, Dec 22, 2008 at 7:43 PM, Kurt wrote:
>
> Stick the code in iframes, then ad those to the page with jQuery.
> That's what we do on arstechnica.com.
>
> The vast majority of ad scripts e
var allItems = $('div.ds-item', datascape);
(...)
$('*', allItems).not('p, a,form').show();
triggers this error in firebug:
Error:
match[3] is undefined
jquery-1.3b1.js
Line 1812
testcase here: http://pixeline.be/experiments/jquerybeta/test1.html
it seems related to the use of the wildcard '*
i've been working on this project for like 2 years now, it's grown so
huge and i've learned so much in the process, that i could probably
just start it all over again, so much of this code is outdated. Thanks
for the pointer :)
On Tue, Dec 23, 2008 at 8:04 AM, Kelvin Luck wrote:
>
>>>
>>> functi
Cool, no problem, glad I could finally contribute back to jQuery in my
tiny way!
I found another bug where selectors like this was being unrecognized
by Sizzle:
input[name='types[]']
When you get time, please review and merge this commit that fixes this
bug into your Github repos (if it's fine
12 matches
Mail list logo
