#13499 closed bug (fixed)
Descendant selector fails when searched ID doesn't exists but NAME does (IE7 only)
| Reported by: | Owned by: | gibson042 | |
|---|---|---|---|
| Priority: | low | Milestone: | 1.10 |
| Component: | selector | Version: | git |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
It seems that jQuery selector with IE7 doesn't behave the right way : in the following example, $("#notes2 textarea") shouldn't match anything -- it does, with an error.
<html>
<head>
<script type="text/javascript" src="http://code.jquery.com/jquery-1.9.1.js"></script>
</head>
<body>
<div id="content">
<textarea name="notes2"></textarea>
</div>
</body>
</html>
The following code ouputs "notes2" - OK
$("#content textarea").attr("name");
$("textarea").attr("name");
The following code ouputs "undefined" - OK
$("#doesntexists textarea").attr("name");
But this one FAILS.
$("#notes2 textarea").attr("name");
In my opinion textarea attribute name "notes2" conflicts with the #notes2 selector.
Change History (9)
comment:1 follow-up: 2 Changed 5 years ago by
comment:2 Changed 5 years ago by
| Owner: | set to cem.moreau@… |
|---|---|
| Status: | new → pending |
comment:3 Changed 5 years ago by
| Status: | pending → new |
|---|
Here is the sandboxed example : http://jsbin.com/ibotuw/3/
Be aware : edit will crash under IE7.
comment:4 Changed 5 years ago by
| Owner: | changed from cem.moreau@… to gibson042 |
|---|---|
| Status: | new → assigned |
Thanks very much. This will be fixed in the next release.
comment:5 Changed 5 years ago by
| Component: | unfiled → selector |
|---|---|
| Milestone: | None → 1.9.2 |
| Priority: | undecided → low |
comment:6 Changed 5 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Fix #13499: selector with leading ID matching only a name
Changeset: 5c4ab97a64c162503ac200bc7cea7f3e5725984d
comment:7 Changed 5 years ago by
Fix #13499: selector with leading ID matching only a name (cherry picked from commit 5c4ab97a64c162503ac200bc7cea7f3e5725984d)
Changeset: 7d36c0fb6e0e97a2f1af31657104d6cbd5d90b64
comment:9 Changed 5 years ago by
| Milestone: | 1.10/2.0 → 1.10 |
|---|

I may be wrong on my diagnosis: I still have the same problem on a more complex page I can't reproduce here, even if I don't have any name conflict.
This is really weird, I hope my first example will enlight the root cause of all this.