Chain command blocks that are set to conditional will not activate if the command block behind it succeeded to execute.

In the attachment, there's an impulse command block pointing at a chain command block that simply performs "/testfor @p". The block nest to it performs "/say true". I've activated the impulse command block and the comparator activated, but not the other chain command block that should've detected the block behind it despite it not pointing in its direction.

This used method to work in 15w35b, however that snapshot has been completely replaced replaced with 15w35e in the profile settings, hence this cannot be tested in that version at least for me.

If this feature was removed on purpose and seen as a bug, then please explain why. I think having a conditional chain command block branching from another is way better and direct than having to use comparators. Comparators even power a block and all the blocks adjacent to the block it's powering, so it can disrupt other command blocks. If there were some good reason why this feature was removed, please tell my why and how it was decided that it's not best for the mechanics.

Update: Here's an explanation of what I expected to happen:
https://youtu.be/k6kxuH9AY4U?t=24m29s