Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

286
Views
Safari and WebKit async anonymous function execution differences

Running this code on Chrome and Safari would be different. Notice, function is async.

(async function(v) {
    console.log(v)
})('@')

Safari out:

1 - '@'

Chrome out:

1 - '@'

Now it look ok, but what if we add some.

(async function(v) {
    console.log(v)
    var v = v || '#';
    console.log(v)
})('@')

Safari out:

1 - undefined
2 - '#'

Chrome out:

1 - '@'
2 - '@'

There are no more passed V as parameter, its voided even right after function body starts. It seems Safari lefthand operator runs first and replace all passed params with the new ones that are defined in a scope. Is this a bug?

about 4 years ago · Juan Pablo Isaza
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!