Steve Gravrock

Closing due to sustained lack of user interest.

This is a bug in Safari. `setTimeout` is very slow in Safari compared to other browsers. Unfortunately Jasmine has to do a `setTimeout` every so often in browsers to allow...

That's a good idea, but (surprisingly to me) `requestAnimationFrame` is *much* slower than `setTimeout` in Safari: 20 seconds instead of 6 seconds to run your example suite. The slowdown is...

> How about `Promise.resolve().then(fn)` (using the job queue instead of the task queue)? On my machine this runs in 0.25 seconds instead of 6.5 seconds. > > From what I...

Sure enough. I get a similar result. `messageChannelImpl` is much slower than `browserQueueMicrotaskImpl` in 15.x and 16.0, but in 16.5 it's about 3x faster for this scenario. It might make...

Hmm. Switching to `messageChannelImpl` speeds up a suite of tests that don't do anything, but it slows jasmine-core's own test suite down significantly. I get around 4.3 seconds (which is...

Another approach would be to ignore the overall performance issue and address focusing specifically, since that's what prompted the original bug report. The reason for all those QueueRunner executions is...

> It's a potentially nasty breaking change to reporters. Now that I've learned a bit more about how the third party packages in the Jasmine ecosystem are (or in many...

You could add the metadata by calling [setSpecProperty or setSuiteProperty](https://jasmine.github.io/api/5.1/global.html#setSpecProperty) and then write it to whatever destination you have in mind with a custom reporter.

`toBeDefined` is an unfortunate relic of the very early (pre-1.3) days, when there was no `.not` and the only way to negate a matcher was to write a second one...