It looks like the ProtoExpectations are indeed getting added for the VideoPlayback, but the video proto expectations are somehow getting filtered out in mergeIntersectingAnimations. The bug has to be somewhere in that code path, because multiple video playback expectations should never get filtered down to zero of them (which is what's happening).

Interesting: the way that we identify a video protoexpectation is that we call pe.containsTypeNames([INITIATOR_TYPE.VIDEO]), which seems to be returning false even for ProtoExpectations. I wonder why?

It looks like the way that we were detecting whether something was a video expectation when determining whether to merge intersecting expectations:

var isVideo = pe.containsTypeNames([INITIATOR_TYPE.VIDEO]);

always returned false, because INITIATOR_TYPE.VIDEO isn't a type name, its the initiator type.

More broadly, we should always be able to just look at the initiator type of the proto expectation to determine what type of proto expectation it is. I'm going to send out a quick CL fixing this.

This was fixed in https://codereview.chromium.org/2778993004/