[Web][FireFox][Windows]: Uncaught Error in Firefox on click event using template app (using Wacom pen) #75559
Assignees
Labels
assigned for triage
issue is assigned to a domain expert for further triage
browser: firefox
only manifests in Firefox
f: gestures
flutter/packages/flutter/gestures repository.
framework
flutter/packages/flutter repository. See also f: labels.
platform-web
Web applications specifically
platform-windows
Building on or for Windows specifically
r: fixed
Issue is closed as already fixed in a newer version
Comments
|
@Leffe108
Is this what are you referring to, that the console is showing flutter doctor -v |
darshankawar
added
in triage
|
I get different exceptions that you and it is not possible for example to use the + button in the sample app due to the exceptions. I do seem to get it consistent on another Windows 10 machine also with Firefox 85.0.1. In both cases I use Swedish as locale in Firefox but in my initial post I had Windows set to some English variant (I think UK) as UI language in Windows while this case it is Swedish. Both cases use same input hardware attached to computer (a wacom bamboo in pen-mode and a kinesis keyboard)
Dev console Log in Firefox |
no-response
bot
removed
the
waiting for customer response
|
I did some more testing by clicking with a Logitec trackball and laptop touchpad instead of with my wacom pen. When I click with the logitec trackball or with laptop touchpad
Conclusion I attach my wacom settings here in case the bug only occur with specific driver settings. |
Leffe108
changed the title
darshankawar
added
browser: firefox
darshankawar
changed the title
|
Thanks for your quick replies. I think the pen should work like a pointer input to click with if Flutter/Firefox don't support extended preasure etc. APIs. But I understand it is a narrow case and there are more general stuff to work on with impact on more users. This bug does not occur in Chrome. |
yjbanov
added
the
assigned for triage
|
@Leffe108 there is a PR fixing a few unhandled exceptions related to pointer events (flutter/engine#24447). It would be great if you could try it out once it lands in master. It may or may not fix your specific pen issue. I'll comment again on this issue once the master channel has the fix. |
mdebbar
added
the
waiting for customer response
|
Hi, The behaviour is different in that I now only get one exception thrown instead of an endless flow of exceptions. Also I cannot reproduce the exceptions consistently. On some app load (Ctrl + R) there is no exception thrown when I click and in other app loads it occur. I have not been able to figure out the reason. First I suspected that I needed to keep my pen off the tablet during load (to not generate any movement events during load), but then I was still not consistently able to reproduce the exception on every reload. Maybe about 30% of the app loads. In both cases (exception thrown or no exception) the number is not incremented when I click on the + button with my pen. The starter app still work fine with my trackball mouse. When I've skimmed the exception it looks like it is the same both when I click on the background or on the + button with my wacom pen, but I attach both in case there are some details in there I didn't see. Click on backgroundClick on FAB + buttonWhen there is no exceptions thrown I only see the frame events that seem to be enabled by default in master? (I never used master channel before). The frame events look like these and occur upon mouse pointer movement: |
no-response
bot
removed
the
waiting for customer response
|
@Leffe108 ok, that's good to know. The continuous assertion errors aren't happening anymore. I deployed the sample counter app with some extra logging here: https://sampleflutterapp-mouaddebbar.vercel.app/ |
|
|
@Leffe108 thanks for the details! I'm working on a fix for this. Once I have the fix ready, I'll deploy it and ask you to try it out if you don't mind. |
|
@Leffe108 here's the fix deployed at: https://sampleflutterapp-mouaddebbar.vercel.app/ Please give it a shot and let me know if it works. If it doesn't, please share what you see in the console. |
|
I have tested it and can no longer reproduce the reported error. I reloaded the app about 10 times as I in the past had it only reproduce in some page loads. Edit: In other words, I can use my wacom pen now to click on the + button to increment the button or click on the background without breaking the app and there are no unhandled exceptions in the log. I do see one visual glitch though and that is that the + icon on the button animates up upon hover but never animates down. This issue is present also with my trackball mouse and not specific to wacom and could be something totally unrelated to this issue. I just never have seen it before. (but I usually only work with beta channel) |
|
Adding some screenshots of the + button thing. Hopefully this is a known unrelated issue, but it could potentially be something with the blur event being broken by your fix?
|
|
I'm glad your pen issue is fixed! I'll merge my PR that fixes it. The |
darshankawar
added
the
r: fixed
|
Thank you for the quick handling of this issue. I tried to reproduce the |
|
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Steps to Reproduce
flutter create bug.flutter run -d web-serverAs an alteranative you can click on the + button which will not work and also just emit uncaught exceptions in F12 console.
Expected results:
I expect no errors in the F12 console, and espcially not uncaught errors from the framework.
Actual results:
I get loads of uncaught errors in the F12 console of Firefox. Also the + button does not work if you click it (it also emit these errors and the business logic that increment the value never runs)
Logs
I have reproduced the errors also when firefox run in safe-mode, disabling all plugins and I have Firefox 85.0.1
The text was updated successfully, but these errors were encountered: