Ticket #4058 (closed bug: fixed)
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: | |
| Blocking: | Blocked by: |
Description
Refer to this group thread.
Attachments
-
index.html
(1.5 KB) -
added by ecentinela 4 years ago.
- chrome find selector
-
find-testcase.htm
(717 bytes) -
added by ricardobeat 4 years ago.
- Short test-case
Change History
Changed 4 years ago by ecentinela
-
attachment
index.html
added
comment:1 Changed 4 years ago by ecentinela
Ooops! I didn't paste the link http://groups.google.com/group/jquery-en/browse_thread/thread/d2ec8b0934be38aa/
comment:2 Changed 4 years ago by ricardobeat
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,
comment:3 Changed 4 years ago by ricardobeat
Forgot to add that this bug only happens if the target element already has a class defined, otherwise everything works fine.
Please follow the bug reporting guidlines and use jsFiddle when providing test cases and demonstrations instead of pasting the code in the ticket.
chrome find selector