Skip to main content

Bug Tracker

Side navigation

#2192 closed bug (fixed)

Opened January 19, 2008 11:34AM UTC

Closed December 10, 2010 12:15AM UTC

strict ~= selector

Reported by: cloudream Owned by: flesler
Priority: minor Milestone: 1.3
Component: selector Version: 1.2.2
Keywords: Cc: cloudream
Blocked by: Blocking:
Attachments (2)
  • 2192.diff (5.0 KB) - added by nathanhammond August 20, 2008 03:14PM UTC.

    Patch.

  • selector.diff (0.5 KB) - added by cloudream January 19, 2008 11:35AM UTC.

    patch for /src/selector.js

Change History (4)

Changed January 26, 2008 09:54PM UTC by davidserduke comment:1

type: enhancementbug

Changed August 19, 2008 12:36PM UTC by flesler comment:2

cc: → cloudream
component: coreselector
milestone: 1.2.31.3
need: ReviewPatch
owner: → flesler
status: newassigned

Changed August 20, 2008 03:21PM UTC by nathanhammon comment:3

I've attached a patch that not only adds support for ~=, but also |=. The only compromise for more common selectors is on file size, and for efficiency, the worst one (|=) gets tested last.

The patch includes updates to the test suite to add tests for these new selectors and updates existing tests where results didn't match anymore.

This should close #2192, #2640, and #2856.

Changed December 10, 2010 12:15AM UTC by jitter comment:4

resolution: → fixed
status: assignedclosed

Correct me if I'm wrong but this should be fixed since approx. jQuery 1.3