Skip to main content

Bug Tracker

Side navigation

#4058 closed bug (fixed)

Opened February 04, 2009 09:02AM UTC

Closed February 07, 2009 04:55PM UTC

Last modified February 10, 2009 03:49PM UTC

Simple selector not working in 1.3.1 with webkit browsers

Reported by: ecentinela Owned by: john
Priority: critical Milestone: 1.3.2
Component: selector Version: 1.3.1
Keywords: chrome find selector Cc:
Blocked by: Blocking:

Refer to this group thread.

Attachments (2)
  • find-testcase.htm (0.7 KB) - added by ricardobeat February 04, 2009 04:56PM UTC.

    Short test-case

  • index.html (1.5 KB) - added by ecentinela February 04, 2009 09:03AM UTC.

    chrome find selector

Change History (5)

Changed February 04, 2009 09:04AM UTC by ecentinela comment:1

Changed February 04, 2009 05:30PM UTC by ricardobeat comment:2

I reduced the test case.

The problem is the call to find() before adding the class. It's like the find() return is cached in some way. I happens only for class selectors, only with find() (children/filter work alright), and happens either using the cached container object or a new one.

Sizzle should be handling the query to querySelectorAll, but container[0].querySelectorAll('.selected') returns the expected results.

Hope that helps,

Changed February 04, 2009 05:59PM UTC by ricardobeat comment:3

Forgot to add that this bug only happens if the target element already has a class defined, otherwise everything works fine.

Changed February 07, 2009 04:55PM UTC by john comment:4

resolution: → fixed
status: newclosed

Fixed in SVN rev [6178].

Changed February 10, 2009 03:49PM UTC by john comment:5

priority: blockercritical