Wow, thanks for the link and clearing out. That's something new I learned today :)
Thanks again. ---- Read jQuery HowTo Resource - http://jquery-howto.blogspot.com On Sat, Jan 17, 2009 at 9:34 PM, B J Pohl <bjp...@gmail.com> wrote: > > Thanks for looking into this! First off, I have complicated my > question by not being careful with my reporting: The selector that > *did* work in fact used a '.' (I missed it above... i.e. $('acomment') > should be $('.acomment')) Sorry about that. > > Further experimenting shows that this behavior is browser specific. I > see the described behavior in Chrome, but not in IE7. (In fact, I've > had to revert to 1.2.6 because the behavior is inconsistent between > browsers). I believe it is related to a bug that has been reported > concerning capitals in class names with Safari(i.e. WebKit): > > http://dev.jquery.com/ticket/3840 > > Anyway, thanks for the feedback! > > On Jan 17, 8:02 am, jQuery Lover <ilovejqu...@gmail.com> wrote: >> I have just spent about 5 minutes trying to select elements without >> "." and also tried to select classes with different capitalization. >> >> None could be selected... Works just fine, as it should be!!! I am >> getting my jquery >> from:http://ajax.googleapis.com/ajax/libs/jquery/1.3/jquery.min.js >> >> ---- >> Read jQuery HowTo Resource - http://jquery-howto.blogspot.com >> >> On Sat, Jan 17, 2009 at 8:25 AM, B J Pohl <bjp...@gmail.com> wrote: >> >> >> >> > Upgraded to 1.3 on my site today and found that previously working >> > code is broken. The issue is that I was using a selector of $ >> > ('.aComment') to get, not surprisingly, elements with a class of >> > 'aComment' . This worked great with 1.2.6. However, with some >> > tinkering, I have found that I can user $('acomment') to select these >> > nodes with 1.3 . >> >> > Question is, is the expected behavior or a bug? I'm pretty new to a >> > lot of this stuff so I acknowledge my ignorance in advance. However, >> > I thought it a weird change in behavior. >> >> > Can someone give me some feedback? If this is a bug, I'll do my best >> > to submit it (and maybe even try a fix). If it isn't, can someone >> > explain to me why the different behavior between 1.2.6 and 1.3? >> >> > Thanks! >> >> > B.J.
