Bug Tracker

#11157 closed bug (duplicate)

Opened January 11, 2012 12:09PM UTC

Closed January 11, 2012 03:30PM UTC

Last modified January 11, 2012 03:30PM UTC

Attribute filter can't deal with colons

Reported by: anonymous Owned by:
Priority: undecided Milestone: None
Component: unfiled Version: 1.7.1
Keywords: Cc:
Blocked by: Blocking:
Description

Given some rss 2.0 it's quite hard to get the content:encoded property. (Tested browser: current Chromium nightly build)

broken:

.find('[nodeName="content:encoded"]')

also broken:

.find('content\\\\:encoded')

workarounds

.find('encoded') // mostly not applicable

.filter(function(){ return this.nodeName === 'content:encoded')

I would have expected the last workaround to be identical to what the attribute filter actually does

Attachments (0)
Change History (2)

Changed January 11, 2012 03:30PM UTC by dmethvin comment:1

resolution: → duplicate
status: new → closed

nodeName is not an attribute (it's a property) so the attribute filter doesn't apply to it. Use .filter() with a function or some other method to look at the property.

Changed January 11, 2012 03:30PM UTC by dmethvin comment:2

Duplicate of #10377.