processor.io's CursoryReader does not recognize when it reaches the origin node
in some cases; so, it continues to return content from its read method if the
origin node has following-siblings.
Original issue reported on code.google.com by joe.bays...@gmail.com on 27 Apr 2015 at 4:58
Original issue reported on code.google.com by
joe.bays...@gmail.com
on 27 Apr 2015 at 4:58