I'm unfamiliar with this type of of injection, but just because I'm unfamiliar with it doesn't mean it isn't real.

That said, the old filterAttr() version can't be used because it relies on the data attribute value in the element, and not on the data object associated by jQuery when using data().  These two are not guaranteed to be the same.  I've crafted a revision that is API compatible with the existing functions (.hide(), .show(), and .remove()), but uses jQuery's .filter() instead.  It's a shame, since extending jQuery's colon selector is such an elegant solution.

Mentioned commit pending after local testing.