Támogatás keresése

Kerülje el a támogatási csalásokat. Sosem kérjük arra, hogy hívjon fel egy telefonszámot vagy osszon meg személyes információkat. Jelentse a gyanús tevékenységeket a „Visszaélés bejelentése” lehetőséggel.

További tudnivalók

A témacsoportot lezárták és archiválták. Tegyen fel új kérdést, ha segítségre van szüksége.

Why does FF show about:blank when launching intent://

more options

When launching an intent:// from android Firefox targeting an installed application, the application does load properly but the browser also opens an about:blank page at the same time. This seems like what is described in a 2013 bugzilla report 827370. The preference is not to clutter the browser with this page as the intent is to instruct the user to "back out" of the application in order to access the last tab on the browser seen. However, with the about:blank page, the user must also dismiss the tab or search for the right tab which is an interruption in workflow and error prone (too high potential for support requirement).

Host OS: Android 5.0 (although issue reported with another user at 5.1.1 using a Samsung SM-T900). FF Version: 41.0

When launching an intent:// from android Firefox targeting an installed application, the application does load properly but the browser also opens an about:blank page at the same time. This seems like what is described in a 2013 bugzilla report 827370. The preference is not to clutter the browser with this page as the intent is to instruct the user to "back out" of the application in order to access the last tab on the browser seen. However, with the about:blank page, the user must also dismiss the tab or search for the right tab which is an interruption in workflow and error prone (too high potential for support requirement). Host OS: Android 5.0 (although issue reported with another user at 5.1.1 using a Samsung SM-T900). FF Version: 41.0

Összes válasz (1)

more options

There was a change in Firefox 41 related to intent:// URIs: https://bugzilla.mozilla.org/show_bug.cgi?id=1198369

Maybe this is a side effect of that change?

Once a bug is closed and the change is released, it usually is best to file a new bug.