Fails in Chrome 75.0.3770.100 @Win 10 full screen
Works as expected in design mode with medium stage.
Don't work at all with small stage (always "not touching")
With default canvas antialiasing single source pixel makes colorful pattern. Resolution, color depth, stage scale may result in different pattern. Maybe there are even no single pixel with exactly this "yellow" touching "green".
Sometimes color matching can be based on range instead of exact. For ex: RGB values with stripped 1-2 lower bits.
Attached screen dump enlarged with Paint.
.
Maybe single pixel-wide objects on edge are unintenionally cropped by rouding of position and/or dimension. I made red pixel sticked to the yellow "nose" and color detection works flawless.
Checked different sprite positions and found that probably first row and first column of pixels is ignored during the touching test. Dad said it's probably a typical problem "does indexing start from 1 or from 0?".
Wow, thanks, team! A bug report with the solution attached is the best kind! :~)
If you have a Github account then Github is best. Certainly for a PR Github is essential. But this bug might not have been fixed so quickly if reported on Github, which has a smaller audience following Snap!, so I don't know for sure. A bug that doesn't get fixed here will end up copied to Github by one of the staff.
Here:
Windows 10 with
FF 68.0.1 (64-Bit) > works fine
Chrome Version 76.0.3809.100 (Official Build) (64-bit) > works also fine
Sorry, I couldn't reproduce the problem.
Yes, it seems to have something to do with the dithering of the sprites in smaller windows. Beyond a certain size (approx. 3 times the usual size) it works good, under that it doesn't touch.