Well, the sane thing to do would be to put in a bug fix in the LWJGL directly then. And since I assume you're not going to roll out the latest version of LWJGL as soon as the problem gets fixed there, really the bug should be fixed in the "Minecraft" branch of LWJGL that you are shipping with Minecraft.
LWJGL is open source after all.
Since it seems as if I've commented on a duplicate bug description (even if that description was better), and that one was closed, I'll copy my comment here:
I have the same problem using my MacBook Pro with a touchpad. First the ctrl-click was removed at 1.6 (how did that even happen?), and then when that issue is "fixed", we get another issue, also rendering the game unplayable.
I must say that I am kind of surprised. Surely there must be someone at Mojang testing the games with a MacBook Pro without mouse? Or is that configuration unthinkable?
This is an insane bug and I can't believe it's still here. Come on, really.
I have the same problem using my MacBook Pro with a touchpad. First the ctrl-click was removed at 1.6 (how did that even happen?), and then when that issue is "fixed", we get another issue, also rendering the game unplayable.
I must say that I am kind of surprised. Surely there must be someone at Mojang testing the games with a MacBook Pro without mouse? Or is that configuration unthinkable?
Yay! It's playable again! Nice work!