Chrome Marking Menu (https://chrome.google.com/extensions/detail/
dhbobbhcjchoconllpepbcanpfbmebgc/) binds itself to the middle-click
event with the following JavaScript:
function onMouseDown(event) {
if (event.button == '1') {
I've received a couple of reports where a user cannot use my extension
because Chrome is eating the mousedown event and instead displaying
the auto-scroll arrows. I know one user tested it under Windows XP
via VMWare on a Mac Pro. I don't know about the other's environment.
I do know it works perfectly on my Mac.
I've done some quick research, and it seems that auto-scroll is baked-
in to the Windows build and not user-togglable:
http://code.google.com/p/chromium/issues/detail?id=12478
Chrome should pipe the mousedown event through the standard JavaScript
event system, and only trigger auto-scroll if the event bubbles past
the root node without being cancelled with event.preventDefault. If
for whatever reason that won't happen, I'd like to see a parameter in
manifest.json whereby an extension can register as an auto-scroll
replacement.
Can someone confirm my suspicions re: the Windows build displaying
auto-scroll arrows instead of dispatching a mousedown event? If this
is truly the case, I'll file a bug report on the issue tracker.
As an extension developer, this is frustrating, but as a web developer
it's infuriating to have Google, a huge proponent of web standards,
blatantly break the relevant spec:
http://www.w3.org/TR/DOM-Level-2-Events/events.html
--
You received this message because you are subscribed to the Google Groups
"Chromium-extensions" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/chromium-extensions?hl=en.
