ReadingTimeTarget selector about reading-time HOT 4 CLOSED

+1 yes, this is annoying and seemingly unecessary

from reading-time.

@disklosr if you're simply looking for the on-page read time, you can actually write something pretty effective with just a few lines, I switched to this to avoid the problem:

var words = $('.post-body').text().trim().split(/\s+/g).length,
    wordsPerMinutes = 270;

$('.read-time').text(Math.ceil(words / wordsPerMinutes) + ' min')

I am still using this plugin, but only for the remote counting functionality.

from reading-time.

The reason why the target is assumed to be a child element of the selector is because there may be multiple articles on the same page, so there needs to be some kind of relationship between the selector and the target. I'm open to suggestions if you can think of a better way to maintain that relationship per article.

from reading-time.

I understand how that is useful functionality. Maybe if passed an object, the assumption should be that the user has taken care of it themselves.

I would expect the following scenarios to be supported:

If I wanted to do the contextualisation myself:

$('.post').each(function() {
  $(this).readTime({readingTimeTarget: $(this).find('.read-time')});
});

If I only have one post and don't care about contextualisation:

var $post = $('.post');

$post.readTime({readingTimeTarget: $post.siblings('.read-time')});

I get why yours works as it does, but I think it differs from the way other plugins implement similar functionality, which makes it a bit confusing.

from reading-time.