I refined the capx further here:
https://dl.dropboxusercontent.com/u/542 ... _bug2.capx
The bug is an "or event" that's a sub-event of an empty event affects a following "or event" that's a sub-event of a "for each" event.
Here's what the events looks like:
The layout has two sprite types: red and blue.
Red has only one instance and can be anywhere. It is only required to have the "for each".
Blue has at least two instances to be able to see the bug.
The gist of the events is to pick the first instance of blue and make it transparent if it's left or above the center of the layout (250,250).
It acts as intended for the first instance of blue, but when event 2 is enabled then event 4 also seems to pick any other instances of blue. The other instances are only picked with the second condition of event 4 though. So if any other instance has a y lower than 250 it becomes transparent.
The expected behavior would be for the other instances to not be picked regardless if event 2 was enabled or not.
If rewritten without using "or", and keeping the same behavior as the bug, the events would look like this:
This was tested in r219 in google chrome 47.