Skip to main content

Bug Tracker

Side navigation

#9394 closed feature (wontfix)

Opened May 22, 2011 07:16PM UTC

Closed June 07, 2011 06:53PM UTC

nextUntil/prevUntil take functions

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

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.

Attachments (0)
Change History (11)

Changed May 22, 2011 07:27PM UTC by john comment:1

keywords: → 1.7-discuss

Nominating ticket for 1.7 discussion.

Changed May 22, 2011 08:31PM UTC by rwaldron comment:2

-1, can be achieved with existing API

Changed May 23, 2011 01:05AM UTC by jaubourg comment:3

-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 :/

Changed May 23, 2011 05:08AM UTC by timmywil comment:4

-1, inflation

Changed May 24, 2011 12:59AM UTC by timmywil comment:5

component: unfiledtraversing
priority: undecidedlow
status: newopen

Changed May 24, 2011 10:25PM UTC by dmethvin comment:6

-1, Creep of the feature kind.

Changed June 03, 2011 02:11PM UTC by john comment:7

-1, Ehh, not terribly excited by this.

Changed June 05, 2011 10:34PM UTC by ajpiano comment:8

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

Changed June 06, 2011 02:55PM UTC by danheberden comment:9


Changed June 06, 2011 03:38PM UTC by scottgonzalez comment:10

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

Changed June 07, 2011 06:53PM UTC by rwaldron comment:11

milestone: 1.next1.7
resolution: → wontfix
status: openclosed

Closing per 1.7 roadmap meeting resolution