-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PanResponder: Firefox problem #729
Comments
I haven't looked into this yet, but it does seem that Firefox is doing something different to other browsers here (cc @linclark) |
I thought I'd fixed this but there's something else going on with Firefox. After the first press-and-drag, it stops firing And this issue doesn't manifest at all in Firefox if you open dev tools and turn on "responsive design mode" (with or without touch is being emulated). You can also "fix" the frozen state at any time by turning on "responsive design mode". So I wonder if there's an issue in desktop Firefox? Edit: looks like a Firefox bug – when a shape has |
cc @miketaylr from mozilla web compat |
agreed, must be a firefox bug.
this is an easily-reproducible example that I can submit to mozilla. thanks for looking into this |
Thanks. @Gregor1971 feel free to report a bug at bugzilla.mozilla.org, or just at webcompat.com and we'll take a look. Thanks! (for bugzilla, you can cc :miketaylr, or just ping me back with the bug number) |
Thank you both |
@miketaylr |
@MillerGregor thanks for filing that issue. The (top) swiper here doesn't always work properly due to this |
Do you want to request a feature or report a bug?
bug
What is the current behavior?
the issue can be reproduced with the example in the RNW Storybook.
What is the expected behavior?
each series of mousedown->drag->mouseup moves the circle with the cursor and leaves it once the mouse button is released.
Environment (include versions). Did this work in previous versions?
OS: Win10 15063
Device: PC
Browser: Firefox 57.0 64bit and Firefox Developer 58.0b8 64bit
React Native for Web (version): 0.1.16 and 0.0.130
React (version): 16.0.0 and 15.5.4
(behavior is the same)
works correctly on:
Clearly, Firefox Quantum is doing something different. I'd submit a bug to mozilla, but they'll want a reproduce-able example. I doubt they'd enjoy receiving my webpacked react app.
thanks
The text was updated successfully, but these errors were encountered: