Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2019.1.0a1
2019.2.0a1
Issue ID
1086987
Regression
No
[WebGL] Input.getAxis() output gets stuck on min/max value when the build is run on Chrome with Evernote Web Clipper extension
How to reproduce:
1. Open attached project ("case_1086987-WebTest-Proj")
2. Build a WebGL build and run it
3. Try moving the cube around using arrow keys, remember the behavior
4. Close it and download Evernote Web Clipper browser extension for Chrome
5. Run the build in Chrome and try moving the cube
Expected results: build behavior remains the same
Actual results: build behavior changes, Input.getaxis output gets stuck on 1 or -1 value
Reproducible with: 2018.3.9f1, 2019.1.0b7, 2019.2.0a8
Notes:
1. Tested with Chrome, Edge, and Firefox, but was only able to reproduce on Chrome
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Resolution Note (2019.3.X):
This appears to be an issue on Evernote side.