Closed
Bug 1907553
Opened 2 years ago
Closed 2 years ago
[Rollout] Websites that had a fall back after 3 seconds don’t load instantly on the second attempt of navigation
Categories
(Core :: DOM: Security, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1884921
People
(Reporter: cfat, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
375.67 KB,
image/gif
|
Details |
[Affected versions]:
- Firefox Release 125.0.3 (Build #20240425211020)
- Firefox Release 126.0 (Build #20240509170740)
- Firefox Release 127.0.2 (Build #20240624183754)
[Affected Platforms]:
- Windows 10 x64
- macOS 14.4
- Ubuntu 22.04 x64
[Prerequisites]:
- Have the latest Firefox Release 128 installed.
- Have a browser profile enrolled in the HTTPS as default protocol rollout (https://experimenter.services.mozilla.com/nimbus/https-as-default-protocoll-in-address-bar/summary).
[Steps to reproduce]:
- Open the browser from the prerequisites.
- Navigate to the http://timeout.httpsonly.polar.onl/ website.
- Open a new tab and navigate again to http://timeout.httpsonly.polar.onl/ website.
- Observe the behavior.
[Expected result]:
- The website is instantly loaded when navigating to it the second time.
[Actual result]:
- The website has a timeout of 3 seconds until is loaded.
[Notes]:
- Attached is a screen recording of the issue.
Comment 1•2 years ago
|
||
This is a good observation, thank you! I indeed didn't think about Bug 1884921 only having landed in 128. For providing a consistent experience, I think I agree that we should move the rollout to only target 128.
Comment 2•2 years ago
|
||
We out to be changing the rollout to target Firefox 128 and above exclusively.
You need to log in
before you can comment on or make changes to this bug.
Description
•