Figure out how to get better stack traces in Safari

[m-mujica]

In #1501 I skipped a test for Safari Mobile.

The version of iOS we were running the test initially is no longer available in Saucelabs. The test breaks on newer iOS versions.

Unfortunately there is no quick fix, since the new stack trace does not include the filename where the error happened, it only points to steal internal's code

This is the original PR where the code was introduced #1374