"LSHIFT" binds and "LSHIFT+BUTTON1" binds (et al) tangled up

[emersonrp]

This might be a well-known quirk or working as intended, but I've noticed today that if I try to bind something to LSHIFT, that bind gets successfully created, but it also creates the same bind for LSHIFT+BUTTON1, per /showbind.  After doing /unbindall, then if I try to bind something to LSHIFT+BUTTON1, it also gets bound to LSHIFT.  The bind fires, in either case, only when LSHIFT is initially pressed, not again on the mouse button press.  The upshot of this is that it doesn't seem possible to bind something to LSHIFT+BUTTON1 that doesn't fire as soon as the shift key is touched.

 

Is this the intended behavior?

 

This is also the case with RSHIFT, LCTRL, and RCTRL at least, I didn't tinker with LALT because it's prebound to +alttray and I use that.  I did notice that LALT+BUTTON1 is bound to +alttray as might be expected from this behavior.

 

 

(And yeah, I realize that if I bind just LSHIFT, I am messing with all possible LSHIFT+ binds, I'm experimenting, here.)