1910538 - clients.boursobank.com - "Suivant" button does not work

Status: RESOLVED FIXED

(Web Compatibility :: Site Reports, defect, P2)

Description

[Calin Tanase]

Environment:
Operating system: Android 11
Firefox version: Firefox Mobile [phone]

Steps to reproduce:

1. Go to https://clients.boursobank.com/connexion
2. Tap on "Saisissez votre identifiant" field.
3. Type "123456789".
4. Tap on "Suivant" button.

Expected Behavior:
Redirected to the next step.

Actual Behavior:
Nothing happens.

Notes:

• Reproduces regardless of the status of ETP
• Reproduces in Firefox Nightly, and Firefox Release
• Does not reproduce in Chrome

Created from https://github.com/webcompat/web-bugs/issues/139642

Comment 1

[Calin Tanase]

Attachment: FF vs Chrome.mp4

Comment 2

[Sky Schubert [:skyschub]]

Seems like some pushState op is throwing a NS_ERROR_FAILURE without an error message.

Comment 3

[Alexandre Poirot [:ochameau]]

For some reason I can't explain, executing this History.prototype.pushState.apply(window.history, [null, null]) throws NS_ERROR_FAILURE,
but only when executing this on that page and only on Fenix.
i.e. doesn't throw on any other page, or on the same page but on desktop.

Note that this page overrides window.history.pushState, that's the reason why I'm using History's prototype.
That snippet is what the page ultimately runs from that override.

Comment 4

[Sean Feng [:sefeng211]]

I am investigating this one

Comment 5

[Sean Feng [:sefeng211]]

I investigated this a bit and figured that button started to work with SessionHistoryInParent is enabled on Android.

Given we are rolling SHIP on Android right now, I think we can leave this bug aside.

I'll also conclude this bug as a platform-bug because the same pushState call works on desktop.

Comment 6

[Calin Tanase]

The issue is still reproducible on the latest Nightly.

Comment 7

[Randell Jesup [:jesup] (needinfo me)]

Can you take another look? Thanks

Comment 8

[Hsin-Yi Tsai (she/her)[:hsinyi]]

FWIW, SHIP is still disabled by default on Android, and there is a WIP to enable SHIP on Android in nightly by default in bug 1951246.

Comment 9

[Sean Feng [:sefeng211]]

Yeah, I think we can leave this as is for now.

Comment 10

[Olli Pettay [:smaug][[e-mail]]]

There aren't that many places in pushState implementation which may throw NS_ERROR_FAILURE.
Didn't see (yet) anything obviously SHIP related

Comment 11

[Calin Tanase]

Retriaged, the issue no longer reproduces on the latest Nightly (140.0a1-20250518220019).

Comment 12

[BugBot [:suhaib / :marco/ :calixte]]

Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.

Comment 13

[railioaie]

Verified as FIXED using RC Build

Tested with:

Browser / Version: Firefox 139.0 Build 2016091866
Operating System: Samsung A51 (Android 11) -1080 × 2400 pixels 20:9 aspect ratio (~405 ppi density)

Comment 14

[Calin Tanase]

This is still reproducible on Release (144) and Beta (145), it works only on Nightly (146).

Comment 15

[Jeff Muizelaar [:jrmuizel]]

We know this is caused by not having SHIP so we don't need needs-diagnosis

Comment 16

[Randell Jesup [:jesup] (needinfo me)]

Fixed in Nightly android (147 should have the fix)