Bug Tracker

Opened 10 years ago

Closed 10 years ago

#9394 closed feature (wontfix)

nextUntil/prevUntil take functions

Reported by: [email protected] Owned by:
Priority: low Milestone: 1.7
Component: traversing Version: 1.6.1
Keywords: 1.7-discuss Cc:
Blocked by: Blocking:

Description

It would be nice if nextUntil and prevUntil could take callbacks rather than selector strings. So the callback would be executed on each sibling in turn. When the function returns true, the selection should end. This would mean that complex selectors would be unnecessary: it would be possible to specify a much more readable (and, I'd guess, faster) function instead.

Change History (11)

comment:1 Changed 10 years ago by john

Keywords: 1.7-discuss added

Nominating ticket for 1.7 discussion.

comment:2 Changed 10 years ago by Rick Waldron

-1, can be achieved with existing API

comment:3 Changed 10 years ago by jaubourg

-1, I dunno, I'd expect selection to be faster and faster... so the idea a function called on all elements of a superset of a selection will be faster :/

comment:4 Changed 10 years ago by timmywil

-1, inflation

comment:5 Changed 10 years ago by timmywil

Component: unfiledtraversing
Priority: undecidedlow
Status: newopen

comment:6 Changed 10 years ago by dmethvin

-1, Creep of the feature kind.

comment:7 Changed 10 years ago by john

-1, Ehh, not terribly excited by this.

comment:8 Changed 10 years ago by ajpiano

+0, Seems like feature creep, but not unreasonable....

comment:9 Changed 10 years ago by danheberden

-1

comment:10 Changed 10 years ago by scottgonzalez

+0, I don't think this actually would be more readable

comment:11 Changed 10 years ago by Rick Waldron

Milestone: 1.next1.7
Resolution: wontfix
Status: openclosed

Closing per 1.7 roadmap meeting resolution

Note: See TracTickets for help on using tickets.