Firefox

20324 readers

215 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

k_o_t@lemmy.ml

golden_zealot@lemmy.ml

101

HTTP warning now has 5s delay before "Continue to HTTP Site" is clickable (lemmy.ml)

submitted 1 year ago by Atemu@lemmy.ml to c/firefox@lemmy.ml

16 comments fedilink hide all child comments

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

[–] gencha@lemm.ee 12 points 1 year ago (3 children)

Does security.dialog_enable_delay work on that?

[–] Atemu@lemmy.ml 8 points 1 year ago (2 children)

It does not. It's also 5s, not 1s, so that couldn't have been it.

Btw, Googling that option, I found out that there's a reason for this delay and it's security: https://www.squarefree.com/2004/07/01/race-conditions-in-security-dialogs/

[–] 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.