Open Bug 1708097 Opened 4 years ago Updated 4 years ago

Clicking "Try Again" on "Server Not Found" page shows flash of "Go Back (Recommended)" button and associated content for 1 frame

Categories

(Firefox :: Security, defect)

Firefox 90
Desktop
All
defect

Tracking

()

Tracking Status
firefox-esr78 --- unaffected
firefox88 --- unaffected
firefox89 --- unaffected
firefox90 --- fix-optional

People

(Reporter: pdehaan, Unassigned)

References

(Regression)

Details

(Keywords: regression, Whiteboard: [foxfooding][community])

Attachments

(1 file)

This comment is copy/pasted from a community issue filed during the Foxfooding program.


Firefox Version: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:90.0) Gecko/20100101 Firefox/90.0
Window Size (inner width and height): 1920x978

Steps to Reproduce

  1. Visit non-existent site (e.g. ergikjmerslkgj.com)
  2. Click "Try Again"

Expected Behavior

Just try again

Actual Behavior

Tries again, but also shows "Go Back (Recommended)" button

Reproduced on macOS 10.15.7/Catalina using Firefox 90.0a1/Nightly, but not 89/Beta or 88/Release.

Attached image try-again-flicker.gif
Priority: -- → P2
Whiteboard: [foxfooding][community] [proton-foxfooding] → [foxfooding][community] [proton-foxfooding] [priority:2a]

This isn't a proton issue. It regressed with bug 1688703, and won't ship with 89. Clearing all the proton flags. Dana, can you take a look? I think this is a side-effect of about:neterror now having to load all the extra cert parsing code.

Component: Foxfooding → Security
Flags: needinfo?(dkeeler)
Keywords: regression
Priority: P2 → --
Regressed by: 1688703
Summary: Clicking "Try Again" on "Server Not Found" page shows "Go Back (Recommended)" button for 1 frame → Clicking "Try Again" on "Server Not Found" page shows flash of "Go Back (Recommended)" button and associated content for 1 frame
Whiteboard: [foxfooding][community] [proton-foxfooding] [priority:2a] → [foxfooding][community]
Has Regression Range: --- → yes

I believe this is a preexisting issue that bug 1688703 made more apparent. Some of the code on that page runs asynchronously, so it makes sense that it's possible to see the page in a broken state before everything has finished running. The page should probably be completely blank until initialization has finished.

Flags: needinfo?(dkeeler)

The page should probably be completely blank until initialization has finished.

I agree, that would probably solve this whole category of (IMO very minor) issues.

Severity: -- → S4
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: