[Snyk] Upgrade webvr-polyfill from 0.9.35 to 0.10.12 #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was automatically created by Snyk using the credentials of a real user.
![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)
Snyk has created this PR to upgrade webvr-polyfill from 0.9.35 to 0.10.12.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 19 versions ahead of your current version.
The recommended version was released on 4 years ago.
Issues fixed by the recommended upgrade:
SNYK-JS-LODASH-1040724
SNYK-JS-LODASH-450202
SNYK-JS-LODASH-567746
SNYK-JS-LODASH-608086
SNYK-JS-LODASH-6139239
SNYK-JS-LODASH-73638
SNYK-JS-LODASH-1018905
SNYK-JS-LODASH-73639
npm:lodash:20180130
Release notes
Package name: webvr-polyfill
0.10.12
Update cardboard-vr-display; 0.10.11
0.10.10
0.10.9
0.10.8
0.10.7
0.10.6
0.10.5
We got reports (#307) of polyfill breakage (thanks @ dustinkerstein!) on newer versions of Chrome. In Chrome m65, a regression to
devicemotion
events doesn't providerotationRate
, breaking the head tracking in the polyfill, and m66 switchingDeviceMotionEvent.rotationRate
values to use degrees instead of radians to be aligned with the spec. Separately there's another issue wheredeviceorientation
/devicemotion
events are fired at 5-10hz in Chrome m65/m66. This doesn't consistently occur.This release includes an updated CardboardVRDisplay with fixes for the
devicemotion
Chrome m65 regression by using adeviceorientation
fallback (immersive-web/cardboard-vr-display@d770e01)and does not take advantage of sensor fusion, and also includes a fix to handle Chrome m66's
rotationRate
unit change (immersive-web/cardboard-vr-display@75a6d51). The issue of lowered device motion rate in Chrome m65/m66 can be tracked at crbug.com/819413. With Sensor API (#10) now being supported instead ofdevicemotion
, one temporary workaround is enabling sensors. Read here to learn more about enabling Sensor API.TLDR: If seeing issues in Chrome m65 and later versions, please update to the latest version of the WebVR Polyfill. There may be some stuttering in the pose due to platform issue on m65/m66, which can be solved locally by enabling
chrome://flags/#enable-generic-sensor
, and there could be a browser update to fix the low frequency rate of device events. Changes have been sent downstream to A-Frame (aframevr/aframe#3453). If upgrading from0.9.x
to0.10.x
, be sure to call theWebVRPolyfill
constructor with your configuration object rather than usingwindow.WebVRConfig
(example).Other Noteworthy Fixes
devicemotion
(#10)vrdisplayconnect
on the polyfilled VRDisplay only if there are no native displays (#303)requestAnimationFrame
incase consumer overwrites, fixes WebVR Unity Exporter issue (#308)Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: