Side navigation
#5075 closed bug (invalid)
Opened August 19, 2009 02:11PM UTC
Closed June 13, 2010 04:36PM UTC
Attribute filters behaviour change since 1.2
Reported by: | iqm | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 1.3.1 |
Component: | unfiled | Version: | 1.3.1 |
Keywords: | attribute filters | Cc: | |
Blocked by: | Blocking: |
Description
when using the statement $("[id^='sel']").length with 2 html select tags on my page with id's of 'selInspector' and 'selPeriods' each having several child nodes (<option />) the length equals 2 in version 1.2.6
The same attribute filter in 1.3.1 returns a number equal to the combined number of the child nodes of both <select/> tags. In my case 382. This means doing something like alert($("[id^='sel']").attr("id")); returns undefined because its actually looking at the first child node. To get the correct id i have to now use alert($("[id^='sel']")parent().attr("id")); I see this as a bug because it doesn't select the object I want but instead returns me the child nodes of the objects I want.
Can you attach a complete test case that demonstrates the problem, and indicate which browsers you used for testing?