[jQuery] Re: IE selector bug/error - now reproducable.
Success - the bug has dissapeared in 1.1.3a ! Thank all. Luc Pestille Web Designer From: jquery-en@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of John Resig Sent: 30 May 2007 17:20 To: jquery-en@googlegroups.com Subject: [jQuery] Re: IE selector bug/error - now reproducable. 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.13a might 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 while Page B has . 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 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 <http://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. <>
[jQuery] Re: IE selector bug/error - now reproducable.
Karl Swedberg escribió:
On May 30, 2007, at 10:53 AM, SeViR wrote:
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 while Page
B has .
Ok, I recognize my error :-P, if you want use the same code in
differents pages using the same id's
in different contexts I could want a selector ".class .id" :)
So, tracing this bug. With a simple test in HTML, with jQuery 1.1.1,
1.1.2 and 1.1.3a I have:
versions 1.1.1 and 1.1.2:
One error getting the element by ID, if I don't have one element with
the class ".class"
jQueryCode > // Try to do a global search by ID, where we can
if ( m[1] == "#" && ret[ret.length-1].getElementById
) { <- error ret[ret.length-1] is undefined
In 1.1.3a:
The bug is fixed and works OK :)
jQueryCode > var elem = ret[ret.length-1];
// Try to do a global search by ID, where we can
if ( m[1] == "#" && elem && elem.getElementById ) {
<- checks first if ret[ret.length-1] is defined
Thanks jQuery team ! :-D
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,
--
Best Regards,
José Francisco Rives Lirola
SeViR CW · Computer Design
http://www.sevir.org
Murcia - Spain
[jQuery] Re: IE selector bug/error - now reproducable.
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 while Page B has . 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. <>
[jQuery] Re: IE selector bug/error - now reproducable.
On 5/30/07, Luc Pestille <[EMAIL PROTECTED]> wrote: 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... Could you please post or attach that most basic HTML page where the error shows up? -- Brandon Aaron
[jQuery] Re: IE selector bug/error - now reproducable.
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.13a might 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 while Page B has . 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 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. <>
[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 while Page B has . 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
[jQuery] Re: IE selector bug/error - now reproducable.
I don't think that ".class #id" generates an error it was a bug of
jQuery because,
simply it is an error this string
#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.
Luc Pestille escribió:
I think I've found a bug in jQuery with regards to IE -a blank .html
page, with just the latest uncompressed jquery.js and a script file
(linked in the header) that looks like this:
/* */
produces an error in IE6 and IE7 (the line number is different in IE7);
---
Line 968
Error: 'getElementById' is null or not an object
---
however, these selectors produce no such error;
$("#search-advanced .classtest").hide();
$(".search-advanced .classtest").hide();
$("#search-advanced").hide();
So it looks like IE doesn't like double ID selectors, or an ID
selector after a space. Anyone seen this before, or can reproduce it?
I'd rather not have to re-write bits of my site to use classes instead
of IDs.
*Luc Pestille*
Web Designer
*From:* jquery-en@googlegroups.com [mailto:[EMAIL PROTECTED]
*On Behalf Of *Luc Pestille
*Sent:* 29 May 2007 09:51
*To:* jquery-en@googlegroups.com
*Subject:* [jQuery] Re: IE selector bug/error?
Anyone have any idea on this? Non-existant selctors are breaking IE,
which is fairly bad news for me!
Thanks,
*Luc Pestille*
Web Designer
*From:* jquery-en@googlegroups.com [mailto:[EMAIL PROTECTED]
*On Behalf Of *Luc Pestille
*Sent:* 23 May 2007 15:19
*To:* jquery-en@googlegroups.com
*Subject:* [jQuery] IE selector bug/error?
I've found something that I can't get around; in IE6, these selectors
won't do anything for me;
1. $("#admin-jobs #discipline_client_row").hide();
2. $("#admin-jobs > #discipline_client_row").hide();
whereas this works fine (as you'd expect);
3. $("#discipline_client_row").hide();
In IE, number 1 gives me the error (when that div doesn't exist on the
page):
---
Line: 184
Error: 'getElementById' is null or not an object
---
but number 2 reports no error, despite not finding the div on the
page. Has anyone come across this before? Any help would be
appreciated, IE is starting to drive me in to a coma.
Thanks,
*Luc Pestille*
Web Designer
In2
Thames House
Mere Park
Dedmere Road
Marlow
Bucks
SL7 1PB
Tel 01628 899700
Fax 01628 899701
e: [EMAIL PROTECTED]
i: www.in2.co.uk
[jQuery] Re: IE selector bug/error - now reproducable.
I'm not able to reproduce this in FF. Your using jQuery 1.1.3a? Is your HTML
valid? Could you post up the test page for the group to look at?
A workaround might be to use .find().
$('.search-advanced').find('#classtest').hide();
--
Brandon Aaron
On 5/30/07, Luc Pestille <[EMAIL PROTECTED]> wrote:
Following on, I was testing something unrelated, after moving back to FF,
and it seems that the bug is the same in FF - ID selectors after a space
break anything! Someone tell me I'm not going mad?
*Luc Pestille*
Web Designer
--
*From:* jquery-en@googlegroups.com [mailto:[EMAIL PROTECTED] *On
Behalf Of *Luc Pestille
*Sent:* 30 May 2007 11:53
*To:* jquery-en@googlegroups.com
*Cc:* John Resig
*Subject:* [jQuery] Re: IE selector bug/error - now reproducable.
I think I've found a bug in jQuery with regards to IE -a blank .html
page, with just the latest uncompressed jquery.js and a script file
(linked in the header) that looks like this:
/* */
produces an error in IE6 and IE7 (the line number is different in IE7);
---
Line 968
Error: 'getElementById' is null or not an object
---
however, these selectors produce no such error;
$("#search-advanced .classtest").hide();
$(".search-advanced .classtest").hide();
$("#search-advanced").hide();
So it looks like IE doesn't like double ID selectors, or an ID selector
after a space. Anyone seen this before, or can reproduce it? I'd rather not
have to re-write bits of my site to use classes instead of IDs.
*Luc Pestille*
Web Designer
--
*From:* jquery-en@googlegroups.com [mailto:[EMAIL PROTECTED] *On
Behalf Of *Luc Pestille
*Sent:* 29 May 2007 09:51
*To:* jquery-en@googlegroups.com
*Subject:* [jQuery] Re: IE selector bug/error?
Anyone have any idea on this? Non-existant selctors are breaking IE,
which is fairly bad news for me!
Thanks,
*Luc Pestille*
Web Designer
--
*From:* jquery-en@googlegroups.com [mailto:[EMAIL PROTECTED] *On
Behalf Of *Luc Pestille
*Sent:* 23 May 2007 15:19
*To:* jquery-en@googlegroups.com
*Subject:* [jQuery] IE selector bug/error?
I've found something that I can't get around; in IE6, these selectors
won't do anything for me;
1. $("#admin-jobs #discipline_client_row").hide();
2. $("#admin-jobs > #discipline_client_row").hide();
whereas this works fine (as you'd expect);
3. $("#discipline_client_row").hide();
In IE, number 1 gives me the error (when that div doesn't exist on the
page):
---
Line: 184
Error: 'getElementById' is null or not an object
---
but number 2 reports no error, despite not finding the div on the page. Has
anyone come across this before? Any help would be appreciated, IE is
starting to drive me in to a coma.
Thanks,
*Luc Pestille*
Web Designer
In2
Thames House
Mere Park
Dedmere Road
Marlow
Bucks
SL7 1PB
Tel 01628 899700
Fax 01628 899701
e: [EMAIL PROTECTED]
i: 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
[EMAIL PROTECTED] and do not necessarily represent those of the
company.
[image: in2 logo]
<>
[jQuery] Re: IE selector bug/error - now reproducable.
Following on, I was testing something unrelated, after moving back to
FF, and it seems that the bug is the same in FF - ID selectors after a
space break anything! Someone tell me I'm not going mad?
Luc Pestille
Web Designer
From: jquery-en@googlegroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Luc Pestille
Sent: 30 May 2007 11:53
To: jquery-en@googlegroups.com
Cc: John Resig
Subject: [jQuery] Re: IE selector bug/error - now reproducable.
I think I've found a bug in jQuery with regards to IE -a blank .html
page, with just the latest uncompressed jquery.js and a script file
(linked in the header) that looks like this:
/* */
produces an error in IE6 and IE7 (the line number is different in IE7);
---
Line 968
Error: 'getElementById' is null or not an object
---
however, these selectors produce no such error;
$("#search-advanced .classtest").hide();
$(".search-advanced .classtest").hide();
$("#search-advanced").hide();
So it looks like IE doesn't like double ID selectors, or an ID selector
after a space. Anyone seen this before, or can reproduce it? I'd rather
not have to re-write bits of my site to use classes instead of IDs.
Luc Pestille
Web Designer
From: jquery-en@googlegroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Luc Pestille
Sent: 29 May 2007 09:51
To: jquery-en@googlegroups.com
Subject: [jQuery] Re: IE selector bug/error?
Anyone have any idea on this? Non-existant selctors are breaking IE,
which is fairly bad news for me!
Thanks,
Luc Pestille
Web Designer
From: jquery-en@googlegroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Luc Pestille
Sent: 23 May 2007 15:19
To: jquery-en@googlegroups.com
Subject: [jQuery] IE selector bug/error?
I've found something that I can't get around; in IE6, these
selectors won't do anything for me;
1. $("#admin-jobs #discipline_client_row").hide();
2. $("#admin-jobs > #discipline_client_row").hide();
whereas this works fine (as you'd expect);
3. $("#discipline_client_row").hide();
In IE, number 1 gives me the error (when that div doesn't exist on the
page):
---
Line: 184
Error: 'getElementById' is null or not an object
---
but number 2 reports no error, despite not finding the div on the page.
Has anyone come across this before? Any help would be appreciated, IE is
starting to drive me in to a coma.
Thanks,
Luc Pestille
Web Designer
In2
Thames House
Mere Park
Dedmere Road
Marlow
Bucks
SL7 1PB
Tel 01628 899700
Fax 01628 899701
e: [EMAIL PROTECTED]
i: www.in2.co.uk <http://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 [EMAIL PROTECTED] and do not necessarily
represent those of the company.
<>
[jQuery] Re: IE selector bug/error - now reproducable.
I think I've found a bug in jQuery with regards to IE -a blank .html
page, with just the latest uncompressed jquery.js and a script file
(linked in the header) that looks like this:
/* */
produces an error in IE6 and IE7 (the line number is different in IE7);
---
Line 968
Error: 'getElementById' is null or not an object
---
however, these selectors produce no such error;
$("#search-advanced .classtest").hide();
$(".search-advanced .classtest").hide();
$("#search-advanced").hide();
So it looks like IE doesn't like double ID selectors, or an ID selector
after a space. Anyone seen this before, or can reproduce it? I'd rather
not have to re-write bits of my site to use classes instead of IDs.
Luc Pestille
Web Designer
From: jquery-en@googlegroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Luc Pestille
Sent: 29 May 2007 09:51
To: jquery-en@googlegroups.com
Subject: [jQuery] Re: IE selector bug/error?
Anyone have any idea on this? Non-existant selctors are breaking IE,
which is fairly bad news for me!
Thanks,
Luc Pestille
Web Designer
From: jquery-en@googlegroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Luc Pestille
Sent: 23 May 2007 15:19
To: jquery-en@googlegroups.com
Subject: [jQuery] IE selector bug/error?
I've found something that I can't get around; in IE6, these
selectors won't do anything for me;
1. $("#admin-jobs #discipline_client_row").hide();
2. $("#admin-jobs > #discipline_client_row").hide();
whereas this works fine (as you'd expect);
3. $("#discipline_client_row").hide();
In IE, number 1 gives me the error (when that div doesn't exist on the
page):
---
Line: 184
Error: 'getElementById' is null or not an object
---
but number 2 reports no error, despite not finding the div on the page.
Has anyone come across this before? Any help would be appreciated, IE is
starting to drive me in to a coma.
Thanks,
Luc Pestille
Web Designer
In2
Thames House
Mere Park
Dedmere Road
Marlow
Bucks
SL7 1PB
Tel 01628 899700
Fax 01628 899701
e: [EMAIL PROTECTED]
i: www.in2.co.uk
