Open Bug 1906323 Opened 1 month ago Updated 2 days ago

Fenix silently fails to load links without WAN connectivity, with no error notification

Categories

(Fenix :: Browser Engine, defect)

All
Android
defect

Tracking

(Not tracked)

People

(Reporter: acreskey, Unassigned)

References

(Blocks 1 open bug)

Details

On a network with no WAN link,Fenix will silently fail to load links with no error notification.

For comparison, Chrome will generally display an error page, e.g. "This site can't be reached".

Steps to reproduce

  1. Load a top news site (e.g. bbc.com, cnn.com, ) in Fenix
  2. Disconnect your wireless access point from the WAN
  3. Click on a link

Expected behavior

An error is displayed or other indication that the pageload failed
In Chrome, the error page displayed is generally "This site can't be reached"

Actual behavior

The pageload progress bar disappears and thus the pageload silently fails without notification

Here's an example profile with nsHttp:5,nsSocketTransport:5,profilermarkers logs as markers.
https://share.firefox.dev/3XL4yil

From the user's perspective, the page load silently fails after about 47 seconds.

Note that while these particular steps to reproduce are artificial (i.e. disconnecting the access point from the WAN), scenarios in which the access point loses connection to WAN are common for mobile users.
e.g.
• wifi on a public transit as it travels between areas of coverage,
• events/venues: device may be able to connect to venue's wifi network, but there may not be stable WAN uplink to handle all users

Device information

  • Firefox version: Fx129, also seeing same behaviour in Fx127, release channel
  • Android device model: Samsung A54
  • Android OS version: 14
Blocks: perf-android

We likely will need to move this bug to the ideal product/component.

See Also: → 1879387

The severity field is not set for this bug.
:boek, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(jboek)
See Also: → 1909562
Severity: -- → S3
Flags: needinfo?(jboek)
You need to log in before you can comment on or make changes to this bug.