@josesanch Hi, it’s a Mozilla bug that was mentioned across several Selenium issues. You are welcome to submit an issue with sone buts of you code/configuration.