FF/browser/Macbook has very low-freq mousemove events compared to FF/Android/Galaxy.S3 and Chrome/Safari/same 2012 Macbook Pro.
I have an app where the user draws on the screen, with mouse in the browser:
document.addEventListener('mousemove', handleMouseMove, false);
However mousemove events seem to come in little bursts, so if I'm waving the mouse around, you can't see enough line to trace the path, just bits of line and dots all over the place. I see the same frequency when I just log the event, and when handling, the time is at worst 2 [Date()-Date()].
FF/Android draws nice lines of dots, as do Chrome and Safari on the Mac. FF is fine on Ubuntu 16.04 on desktop.
Seems like a bug? Should at least be configgable.
Also 'Upload images' just spins on uploading. I'm inclined to just list FF as unsupported on Mac.
தீர்வு தேர்ந்தெடுக்கப்பட்டது
Go to about:config and set dom.event.coalesce_mouse_move = false.
Restart the browser.
Check if it helps.
Read this answer in context 👍 1All Replies (10)
This sounds more like mouse or security software caused problem and not Browser related. There is no AFAIK line tracing on the Browser in default installs.
> Also 'Upload images' just spins on uploading.
That's 'Add images: Browse' in the Question/bug form.
Hah, it works here. Safari, then FF versions shown, same hand dynamics.
WestEnd said
This sounds more like mouse or security software caused problem and not Browser related. There is no AFAIK line tracing on the Browser in default installs.
Mouse works fine with all other progs on machine. If security, personal-use Chrome with a bunch of security add-ons doesn't show it, and the FF install is vanilla for dev purposes, tried switching personal use once but never worked, tho it's my browser on Ubuntu.
What does line tracing have to do with it? Did you see the pics?
I thought that surely FF, with the 7 threads I've granted it, must be very busy not to notice my puny actions, and found the Performance profiler. Turns out that Idle has 98%, see pic.
On Android/Galaxy.S3, FF generates events like the others, tho the rendering lags.
In this case, maybe a single (priority?) number for mouse movement tracking isn't right for the MacOS mouse.
தீர்வு தேர்ந்தெடுக்கப்பட்டது
Go to about:config and set dom.event.coalesce_mouse_move = false.
Restart the browser.
Check if it helps.
TyDraniu மூலமாக திருத்தப்பட்டது
Solved, thanks! I think it needs to be more exposed, since searching didn't turn up anything. Maybe this issue will be enough.
> dom.event.coalesce_mouse_move = false
On the upload issue, best to convert .png screenshots to .jpg before unloading: worth mentioning next to the 'upload pic' button.
Photo: hidden fort of the mind to go with the config. :-)
I also question whether the setting has any value. I'd be inclined to make it an adaptive behavior. The var and the touch equiv are true on my old Android OS, but doesn't cause unusable tracking.
The problem recurs with 65.0 (64-bit). Setting remains, but original behavior is seen; also tried resetting/restarting.
I have the app online now, so you can see it happen: