I think I recognize the bug that you're talking about, and I'm fairly certain it was fixed in 1.1.3a. Let us know once you've had an opportunity to verify this.
--John On 5/30/07, Luc Pestille <[EMAIL PROTECTED]> wrote:
Karl - I'm using 1.1.2 (from the front page of jQuery.com) - I'll try 1.1.3a tomorrow and see if it fixes things (although I've reverted to ".classname .classname" as a selector in the meantime to appease the IE gods. I think I might have confused the issue with my initial ".classname #id" selector, it was merely to highlight the "#id" as the second in a string, "#id #id2" gives the same error - and yes, there is a reason to double-dip with ids, I need the specificity. Brandon - it's not a question of HTML validity - the error shows up even with the most basic of HTML page. It might be a moot point though, 1.1.13amight have already fixed it... Thanks all. *Luc Pestille* Web Designer ------------------------------ *From:* jquery-en@googlegroups.com [mailto:[EMAIL PROTECTED] *On Behalf Of *Karl Swedberg *Sent:* 30 May 2007 16:32 *To:* jquery-en@googlegroups.com *Subject:* [jQuery] Re: IE selector bug/error - now reproducable. On May 30, 2007, at 10:53 AM, SeViR wrote: #id .class <- get the element with id "id" only if has the class "class" but.. .class #id ¿?¿?¿? If you can get the element with id "id", why don't you select directly? #id The id is unique so you don't need preselect a class first. Also, if you want select the element #id and all the elements .class, then ".class, #id" works. This paragraph from the reference section of the upcoming Learning jQuery book might help explain why someone would want or need to preselect a class first. It discusses specifying a tag name rather than a class, but the same principle applies: It might not be immediately clear why someone might want to specify a tag name associated with a particular id, since that id needs to be unique anyway. However, some situations in which parts of the DOM are user-generated may require a more specific expression to avoid false positives. Furthermore, when the same script is run on more than one page, it might be necessary to identify the id's element, since the pages could be associating the same id with different elements. For example, Page A might have <h1 id='title'> while Page B has <h2 id='title'>. As to the bug -- Luc, what version of jQuery are you using? I seem to recall this bug being fixed at some point, though my memory could be deceiving me. If you test it with 1.1.3a and it still produces the error, perhaps you could log it in the bug tracker? http://jquery.com/dev/bugs/new/ thanks, --Karl _________________ Karl Swedberg www.englishrules.com www.learningjquery.com [image: in2 is part of the BWP Group] in2, Thames House, Mere Park, Dedmere Road, Marlow, Bucks, SL7 1PB tel: +44 (1628) 899700 | fax: +44 (1628) 899701 | email: [EMAIL PROTECTED] | web: www.in2.co.uk This message (and any associated files) is intended only for the use of jquery-en@googlegroups.com and may contain information that is confidential, subject to copyright or constitutes a trade secret. If you are not jquery-en@googlegroups.com you are hereby notified that any dissemination, copying or distribution of this message, or files associated with this message, is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Messages sent to and from us may be monitored. Any views or opinions presented are solely those of the author jquery-en@googlegroups.com and do not necessarily represent those of the company.
<<inline: in2logo_long.gif>>
