126680 2014-01-08 21:57:13 -0800 Incorrect this value for callbacks (like requestAnimationFrame) 2022-09-03 06:42:29 -0700 1 1 1 Unclassified WebKit WebCore JavaScript 528+ (Nightly build) Unspecified Unspecified RESOLVED CONFIGURATION CHANGED http://jsfiddle.net/3BLzU/2/ P2 Normal --- 1 bzbarsky webkit-unassigned ahmad.saleem792 andrea.giammarchi ap dbates dino ggaren john.david.dalton oliver oldest_to_newest 965779 0 bzbarsky 2014-01-08 21:57:13 -0800 Steps to reproduce: Load this testcase: <script> function f() { "use strict"; alert(this + ""); } requestAnimationFrame(f); </script> Expected result: Alert saying either "null" or "undefined", preferably the latter. Actual result: Alert saying 'function f() { "use strict"; alert(this + ""); }' Additional information: Per WebIDL spec, the callback this value is set to null, by default, though it should probably be undefined instead (see <https://www.w3.org/Bugs/Public/show_bug.cgi?id=24248>). The requestAnimationFrame specification doesn't say to pass any special this value. So in this case the this value should be undefined, or at worst null, not the function object being called. 1034083 1 ap 2014-09-08 23:45:44 -0700 *** Bug 136635 has been marked as a duplicate of this bug. *** 1896027 2 ahmad.saleem792 2022-09-03 06:42:29 -0700 I am not able to reproduce this bug in Safari Technology Preview 152 and it shows "undefined' for JSFiddle from URL field in all other browsers (Chrome Canary 107, Firefox Nightly 106) as well and also in STP 152. I am going to mark this as "RESOLVED CONFIGURATION CHANGED" since all browsers are matching and showing "Expected Results". Thanks!