Expected: the Redstone will never be off.
Reality:

)
I think this majorly happens if the moving redstone Contact starts moving infornt of a stationary redstone contact.

This seems like a more fundamental bug that affects, Redstone Contacts, Portable Interfaces and maybe other MovementBehavior descendants. It has something to do with startMoving, stopMoving, visitNewPosition and logic of activating/deactivating things.

It would be nice to have a list of expected behaviors for all blocks in all movement modes: [place when anchor destroyed, never place, place near initial]

Things of concern would be:

• Contacts (when starting and stopping in "snap" and "never snap" settings)
• Portable * interfaces (same as above)
• Dispensers
• Deployers
• probably others
• miners (sideways)

This issue has been marked as stale because it has been inactive for 3 weeks. It will be closed if it remains inactive for another 3 weeks.

This issue has been closed since it has been inactive for 3 weeks since it was marked as stale.

Expected: redstone outputs, because two redstone contacts are touching each other (irrelevant to the snap mode)

in my test, for the case above i first get a brief pulse

I believe this happens because of the exact same mechanism. so Don't mind me excavating 2-year-old thread.

Expected: redstone outputs, because two redstone contacts are touching each other (irrelevant to the snap mode)

I also should have mentioned that it is 1.16 modpack environment