Why should pass window object for calling it's methods?

[the-dr-lazy]

I'm just curious about the pattern used in this standard library API for interacting with JavaScript window object methods.
Why should pass window object every time calling an effectful function like requestAnimationFrame?

requestAnimationFrame :: Window -> Effect Unit -> Effect RequestAnimationFrameId

-- Why not this?
requestAnimationFrame :: Effect Unit -> Effect RequestAnimationFrameId

[hdgarrood]

I think requiring the window argument is preferable because it means that you don’t need to make any assumptions about what’s available in the global scope. Not all JS environments have a window global, eg Node.

[the-dr-lazy]

But isn't this library based on w3c standard?
Lot's of functions in this library is just for working with browser API (DOM, History, Navigator, Location) and doesn't work in Node.js.

[hdgarrood]

Yes, I know; my point is that the Window argument means that this is visible in the type.

[the-dr-lazy]

That makes sense, thank you.