kittensgame stopped showing alerts in Firefox

[Former user]

I noticed a checkbox when Transcending and then Adoring saying that if I checked it, I would not get these alerts again. But now I can't Adore, or import a Save or anything that requires an alert.

I can however open up my save in Chrome and there I can adore just fine and the alert shows up asking me if I really want to adore.

I have been looking there is a website specific setting in Privacy and Security, but can't find anything. I have also tried turning off uBlock if that was blocking anything, but no change.

Is that checkbox something that has been in the game? I can't find that text in the source code, but I can't remember the exact text of the checkbox.

[Arima B.]

This is very browser specific. Aside from game’s option’s “show no confirmation” we have no control over how browser handles confirmation dialogs.

[Carl-Johan Kjellander]

TL;DR closing the tab and loading the game again fixed the problem. CTRL-SHIFT-R did not fix the problem.

I decoded and unzipped a couple of save files and I could see that noConfirm was false both before and after I clicked the checkbox. So it had to be on my end, cause turning off confirmations inside Kittens Game worked around the issue. I was searching like crazy inside Firefox for a way to undo this, but there was nothing in Popups, since they weren’t popups. After figuring out what to search for the suggestion was to try CTRL-SHIFT-R to clear the cache, but that didn’t work either.

Finally I found a page that said that this was a protection to hinder malicious sites, and it was only temporary. So closing the tab and opening the game in a new one removed this protection again. So for future reference, this is not a bug, and can be fixed but just closing the tab. The reason it came up on the Transcend dialog, was probably that I had tried to transcend several levels in quick succession (with not enough epiphany) a while back so that dialog came up to fast and this triggered the checkbox to be displayed.

So, not a bug, but you can point users here if this happens to anyone else.

‌