window.requestAnimationFrame must not be writable
Reported by
andersse...@gmail.com,
Nov 13 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:56.0) Gecko/20100101 Firefox/56.0 Steps to reproduce the problem: 1. open console 2. type 'window.requestAnimationFrame = undefined' What is the expected behavior? window.requesAnimationFrame still points to the native function What went wrong? window.requestAnimationFrame is undefined Did this work before? N/A Chrome version: <Copy from: 'about:ve62.0.3202.89 (Official Build) (64-bit)rsion'> Channel: stable OS Version: 4bc124ea2934343d106df5b937e78ce311311658-refs/branch-heads/3202@{#775} Flash Version: 27.0.0.183 /home/user/.config/google-chrome/PepperFlash/27.0.0.183/libpepflashplayer.so
,
Nov 14 2017
Able to reproduce this issue on reported version 62.0.3202.89 and latest Canary 64.0.3265.0 using Windows 10, Ubuntu 14.04 and Mac 10.12.6. The issue is seen from M-50 (50.0.2637.0). Hence considering this issue as Non-Regression and marking it as Untriaged.
,
Nov 14 2017
,
Nov 15 2017
,
Nov 15 2017
,
Mar 19 2018
Works as intended. Some libraries make use of the behavior, monkey-patching in their own requestAnimationFrame function to ensure their code runs before and/or after their users' rAF callbacks. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by woxxom@gmail.com
, Nov 14 2017