Modify ↓
Ticket #11826 (closed bug: fixed)
Explore a parsed caching system for matchesSelector within Sizzle
| Reported by: | timmywil | Owned by: | timmywil |
|---|---|---|---|
| Priority: | high | Milestone: | 1.8 |
| Component: | selector | Version: | 1.7.2 |
| Keywords: | Cc: | ||
| Blocking: | Blocked by: |
Description
Explore a parsed selection cache that would hold 50 (or however many) of the most recent selectors already parsed. This would remove the need for quickIs in event and make matchesSelector use in event delegation much faster.
Change History
comment:1 Changed 13 months ago by timmywil
- Owner set to timmywil
- Priority changed from undecided to high
- Status changed from new to assigned
- Component changed from unfiled to selector
- Milestone changed from None to 1.next
comment:3 Changed 12 months ago by timmywil
- Status changed from assigned to closed
- Resolution set to fixed
Move quickIs to Sizzle; Remove duplicate id matching in init; Added selector caching to Sizzle. Fixes #11826.
Changeset: 713cc8609637a943f77039726d96f5e9f7a36f2b
Please follow the bug reporting guidlines and use jsFiddle when providing test cases and demonstrations instead of pasting the code in the ticket.
Note: See
TracTickets for help on using
tickets.
