this post was submitted on 22 Jan 2024
101 points (99.0% liked)

Firefox

20324 readers
226 users here now

/c/firefox

A place to discuss the news and latest developments on the open-source browser Firefox.


Rules

1. Adhere to the instance rules

2. Be kind to one another

3. Communicate in a civil manner


Reporting

If you would like to bring an issue to the moderators attention, please use the "Create Report" feature on the offending comment or post and it will be reviewed as time allows.


founded 5 years ago
MODERATORS
 

This has started happening a while ago (previously there was not perceptible delay) and luckily I don't have to visit HTTP sites very often but it is annoying and I would like to get rid of it.

I know HTTP is bad TYVM. I only use this HTTPS-only mode to forcibly upgrade to HTTPS whenever possible and be notified if it doesn't work.

Does anyone know why this is happening and how to disable it?

#Firefox @firefox@lemmy.world

you are viewing a single comment's thread
view the rest of the comments
[โ€“] mjurgens@discuss.tchncs.de 4 points 1 year ago* (last edited 1 year ago) (1 children)

That timeout should indeed only last the value of security.dialog_enable_delay, so 1s. If it is 5s for you, it would be nice if you write a bug report, maybe with a screen recording.

[โ€“] Atemu@lemmy.ml 3 points 1 year ago

Huh, after a restart it appears to honour that setting; it's now 1s and that's an acceptable security trade-off.

I'm not 100% sure but there may have been an update that was applied by the restart.