Well, I've tested all four modes and what I'm getting instead is this:
I wonder if your notes as to seen behavior got mixed up as they seem wrong for the mode behavior.LOW: ISR fired once when pin changes from low to high
This mode is seldom used as it causes a continuous interrupt as long as the signal remains low. As soon as your ISR finishes a new interrupt will be generated as soon as your sketch completes a single machine instruction, a very problematic situation.CHANGE: ISR fired continuously while pin is low, no action when pin is high
Sounds like wrong observation as this mode causes an interrupt only on signal transition from low to high or high to low, continuous low or high signals will not generate a interrupt.RISING: works as expected
Should interrupt only of signal going from low to high.
FALLING: Same as CHANGE
Should only interrupt on signal going from high to low but not also low to high as in CHANGE mode.
Note that interrupts generated from simple switch buttons will frequently cause big problems due to contact bounce. There must have good contact debouncing strategy employed to use mechanical switches to generate interrupt signals.
And the golden rule to using ISR coding is to keep the ISR as simple and short as possible, usually just setting or resetting byte size flag global static variable types and let the main loop code test the flag to actually accomplish the task that the interrupt represents and then set or reset the flag variable as applicable.