IMO MicroB will just have to look for movement (beyond some threshold) after a mousedown event and then determine if this should be a call for scrolling or used as part of a javascript event.

Mousedown capability is important though, you run into all the time on sites with JS. (Pulldown menus as one common example.)

There are other problems with MicroB, but it's exciting that there will now be an "open" chance to improve the browser.

My top two issues are:

1) MicroB doesn't always know when to bring up the onscreen keyboard, *especially* on layers that are made visible. For example touch on "search" on this forum, the search form will appear, but it's non-functional.

2) Form submit buttons and select elements do not respect CSS color styling. (Oddly they will take background images though) Rather they end up using a combination of theme colors and some default settings. For most people the result is just white/black buttons everywhere, so it's not deadly. But it's a personal issue for me as the intranet app I've developed uses a lot of button color coding for quick identification. There is a bugzilla report on this one I know. Just hope someone is working on it. Wish I knew enough.