1872144 - Some navigation links and buttons in websites temporarily cause the website to reload

Status: RESOLVED WORKSFORME

(Firefox for Android :: Browser Engine, defect)

Description

[Denis Müller [:Webworkr]]

Steps to reproduce:

Fill out a web form such as multiple selection of items.

Actual results:

When you submit the form, the page unexpectedly reloads.

Expected results:

The submit form process should be executed properly.

Comment 1

[Denis Müller [:Webworkr]]

The phenomenon has occurred since some versions of Firefox Nightly.

123.0a1 (Build #2015993831), 12d395982e+
GV: 123.0a1-20231225214719
AS: 123.20231222050320

Samsung Galaxy A13 5G (SM-A136B)
Android 13

Comment 2

[Denis Müller [:Webworkr]]

Examples:

• https://mmail.all-inkl.com (access required)
• https://e-government.hannover-stadt.de/impulsweb.nsf

On the other hand, the problem does not occur with F-Droid's Fennec after initial testing.
121.0.0 (Build #1210000), 1955f8455f+
GV: 121.0-20231221161100
AS: 121.0

Comment 3

[Lorand Janos]

Hi Denis!

I've tried reproducing the issue you mentioned, using the second example link, on today's Nightly build (123.0a1 from 2023-12-27).

I managed to fill in all the fields, select something on the ones with selection and submitting the form got me to the next page which had new fields which also were selectable and the form was submitted successfully.

I used a close device to which you reproduce this issue with: Samsung Galaxy S23 Ultra (Android 14).

Could you try this on Chrome or other browsers as well? Did you have a clean build, with no navigation history, addons or settings changed? If not, please try the same on a clean build.

Thank you!

Comment 4

[Jonathan Almeida [:jonalmeida]]

Thanks for reporting Denis! Since our QA team weren't able to reproduce this either, could you help us by recording a video of the bug happening so we can see if there is something else that might be causing it?

(In reply to Lorand Janos from comment #3)

Could you try this on Chrome or other browsers as well? Did you have a clean build, with no navigation history, addons or settings changed? If not, please try the same on a clean build.

Could you also try to follow the instructions from Lorand as well?

Comment 5

[Jonathan Almeida [:jonalmeida]]

I suspect this is related to bug 1872170.

Comment 6

[Lorand Janos]

Since the issue related would mean a fix for this one as well, and since it wasn't reproducible on our end either, I'll close this ticket as worksforme.

Comment 7

[Denis Müller [:Webworkr]]

Sorry for the late reply! In the meantime I switched to Fennec. In the last few days I tested again under Nightly due to the Bugzilla request and can confirm that the phenomenon no longer occurs. Thank you

123.0a1 (Build #2015996327), e58472c627+
GV: 123.0a1-20240107090723
AS: 123.20240106050300

Comment 8

[Denis Müller [:Webworkr]]

Can anyone confirm that the problem has now reoccurred? Thanks

Nightly
124.0a1 (Build #2016002087), 89dca41708+
GV: 124.0a1-20240205205906
AS: 124.20240206050329

Comment 9

[Delia Pop (Android QA)]

Hi Denis, I cannot reproduce this issue on the latest Nightly using the links provided in Comment 2. Could you please attach a video recording of the issue and other websites to try this on? Thanks!

Comment 10

[Denis Müller [:Webworkr]]

Currently, this phenomenon only observes in the logged in mobile webmailer.
The published email address for bugzilla is forwarding. I currently see no way to hide the e-mail address of the target mailbox or an alternative test mailbox in a video. In addition, I have to clarify that my current recorder still works correctly and if necessary get a replacement for my screen recorder. The software reports compatibility problems. This is probably due to the update to Android 14.

Do you have a tip for an alternative tracker-free (!) software or can you give me an indication of how I can make elements of a video unrecognizable?

A free web hosting package can be booked at https://all-inkl.com/webhosting/test-account/. It also contains 5 mailboxes where the behavior in the webmailer can be examined. The page all-inkl.com cannot currently be switched to English, I think. However, the tools like webmailers are designed in multilingual language.

At the same time, I also contacted my provider all-inkl.com. In this case, the cause may be in the application itself.

Comment 11

[Delia Pop (Android QA)]

Hi Denis, thanks for providing the additional info. I am still unable to reproduce your issue on the latest releases with Google Pixel 8 Pro (Android 14), but I'll update the ticket to "NEW" for further investigation. Please let us know if you find out if the all-inkl.com is the culprit in the meantime.
Regarding your question, unfortunately I don't have any recommendations for an alternative app to use on mobile, but you could edit any screen recording from mobile on Desktop, using common editing tools, e.g. Davinci Resolve, which is free.

Comment 12

[Denis Müller [:Webworkr]]

Hi Delia,

• Have you tried a test account/test mailbox?
• The response from the provider will probably take some time because support will probably have delegated my email back to the specialist department. The provider is aware of this ticket.

Comment 13

[Denis Müller [:Webworkr]]

Hi Delia,

why did you mark Firefox123 as affected? My original report included version 124. Is this based on bug 1872170? Thanks

Comment 14

[Denis Müller [:Webworkr]]

Thanks for your tip regarding “Davinci Resolve”. I'll take a look when I get the chance. I don't currently have a desktop computer in use. In another context, I came across “Record You” (https://f-droid.org/en/packages/com.bnyro.recorder/). I'll have to see how I get on with the app.

Comment 15

[BugBot [:suhaib / :marco]]

The Bugbug bot thinks this bug should belong to the 'Fenix::Browser Engine' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 16

[Denis Müller [:Webworkr]]

I have not yet received a reply from the provider to my last email dated 29.02.2024 17:04 (Berlin). However, the phenomenon described has recently stopped occurring. I would now wait another two weeks and if it is no longer observed, then this bug report should be closed. Either the problem has been fixed by ISP. In that case, however, they would probably have informed me or the problem was solved unknowingly by a code update in the browser.

Comment 17

[Denis Müller [:Webworkr]]

I have contacted my provider again and am now waiting for the answer.

Comment 18

[Denis Müller [:Webworkr]]

My provider has replied:

"[...] unfortunately this could not be reproduced by our programmers.

We are continuously improving our systems. Presumably this has fixed it. You can therefore close the ticket.

[...]"