We currently have two different methods for running tasks in content processes from tests. ContentTask.spawn and SpecialPowers.spawn. SpecialPowers.spawn is the better choice so you should use that going forward. I've just landed patches that migrate most uses of ContentTask.spawn to SpecialPowers.spawn and a lint rule that will give you an error if you attempt to use ContentTask.spawn.
I couldn't easily migrate some cases. The two APIs have slightly different timings and APIs available to the tasks. In many cases, the tests didn't pass locally on my machine, making testing the migration impossible. It would be appreciated if you could look at the tests that weren't migrated and if you own them, handle the migration so we can completely remove ContentTask.spawn. https://searchfox.org/firefox-main/search?q=eslint-disable-next-line%20mozilla%2Freject-contenttask-spawn&path= -- You received this message because you are subscribed to the Google Groups "[email protected]" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/CAPMxTNq7T4dSko9snLXfBW_YDqw3YPrpEPrFfbWfEK81yk6dTg%40mail.gmail.com.
