Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Delay before able to click "Continue to HTTP Site" on macOS HTTPS-Only Mode

  • 2 பதிலளிப்புகள்
  • 0 இந்த பிரச்னைகள் உள்ளது
  • 2 views
  • Last reply by Mark Engelmann

Mark Engelmann
Mark Engelmann
more options

I'm using Firefox 122.0.1 on macOS 14.2.1. When in HTTPS-Only Mode, some sites only support HTTP, and a screen appears that allows one to click Continue to HTTP Site to continue.

When this happens, it takes a few seconds before I can click the button or before mousing over it highlights the button. Is this intended behavior? My previous Windows 10 computer did not behave this way, allowing me to click or highlight the button immediately.

I'm using Firefox 122.0.1 on macOS 14.2.1. When in HTTPS-Only Mode, some sites only support HTTP, and a screen appears that allows one to click [[HTTPS-Only Mode in Firefox|Continue to HTTP Site]] to continue. When this happens, it takes a few seconds before I can click the button or before mousing over it highlights the button. Is this intended behavior? My previous Windows 10 computer did not behave this way, allowing me to click or highlight the button immediately.

All Replies (2)

zeroknight
zeroknight
more options

There is an intentional one second delay before the button becomes clickable so you can't accidentally skip the warning. This is customizable with security.dialog_enable_delay in about:config.

Mark Engelmann
Mark Engelmann கேள்வியின் உரிமையாளர்
more options

I tried changing this to 0, and it didn't affect the delay at all. And this delay is about 4 seconds, not the 1 second (1000 ms) that this setting was set to.

However, after starting in Troubleshoot Mode this did fix the problem. Earlier, I had disabled my extensions (and I use the default theme), and this hadn't fixed the issue—but I hadn't tried the proper Troubleshoot Mode. I'll have to assume there's something else causing the issue.