Ko tenda hembiapoite sa’ivéta oñemba’apokuévo hese hembiapo porãve hag̃ua. Peteĩ jehaipyre nomoĩporãiramo ne apañuái ha eporanduséramo, roguerekohína ore nepytyvõ rekoha ikatútava ndeykeko @FirefoxSupport Twitter-pe ha avei /r/firefox Reddit-pe.

Avatar for Username

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

Ko téma oñeñongatúma. Ejapo porandu pyahu eikotevẽramo pytyvõ.

Page reloads when switching apps

  • 2 Mbohovái
  • 3 oguereko ko apañuãi
  • 7 Hecha
  • Mbohovái ipaháva peter404

abal0rio
abal0rio
more options

Often, when I switch from Mozilla to a different app and then back, Mozilla seems to reload the page I left off from. This can be immensely frustrating, and I don't know how to avoid this issue.

For example, say I am filling out a form on a website. I need to switch to an app, say telegram or WhatsApp, to copy someone's telephone number. When I now switch back to the website in Mozilla, the page is being reloaded - all my previously entered data is gone, and I have to start from scratch.

Any ideas what I'm doing wrong?

Often, when I switch from Mozilla to a different app and then back, Mozilla seems to reload the page I left off from. This can be immensely frustrating, and I don't know how to avoid this issue. For example, say I am filling out a form on a website. I need to switch to an app, say telegram or WhatsApp, to copy someone's telephone number. When I now switch back to the website in Mozilla, the page is being reloaded - all my previously entered data is gone, and I have to start from scratch. Any ideas what I'm doing wrong?

Opaite Mbohovái (2)

Paul
Paul
  • Moderator
  • Top 10 Contributor
more options

Hi

This is something that our developers are aware of and are looking into. You can follow progress and add comments at:

https://github.com/mozilla-mobile/fenix/issues/12731

peter404
peter404
more options

From what I can tell by looking at the github link, code was added in August to try to diagnose the issue, but no changes to fix anything yet. This does not seem to be a very high priority for the developers.