#5080 closed defect (fixed)
expose css selector definition on dojo.query
Reported by: | Dustin Machi | Owned by: | alex |
---|---|---|---|
Priority: | high | Milestone: | 1.1 |
Component: | Query | Version: | 0.9 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
Right now it is not possible to implement custom css selectors (admittedly non standard). The code is hidden in dojo.query, exposing it would allow external code to modify and add these things as necessary while not sacrificing performance for those who don't.
Change History (2)
comment:1 Changed 13 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:2 Changed 12 years ago by
Component: | General → Query |
---|
Note: See
TracTickets for help on using
tickets.
custom pseudo-selectors are exposed via
dojo.query.pseudos
. This is a map of pseudo-selector names to selector match functions, and this mapping can be extended. Exposing other query operators is not feasible since the burden of implementing the selector twice (once for xpath, once for DOM) seems too high.