Шукати в статтях підтримки

Остерігайтеся нападів зловмисників. Mozilla ніколи не просить вас зателефонувати, надіслати номер телефону у повідомленні або поділитися з кимось особистими даними. Будь ласка, повідомте про підозрілі дії за допомогою меню “Повідомити про зловживання”

Докладніше

Ця тема перенесена в архів. Якщо вам потрібна допомога, запитайте.

Reapparance in FF124 of problem "External link not opening if no window is open on startup", from FF 117+ fixed

  • 1 відповідь
  • 2 мають цю проблему
  • 16 переглядів
  • Остання відповідь від Infinity__

more options

[With ~Ff 123?8 and now 124 installed on iOS 17.3 platform updated a couple weeks ago from iOS 15.+ on my iPhone XR]

  For couple weeks , following any external link/reference, such as all 'unsubscribe' links from Apple Mail messages, Firefox opens but homepage rather than to the link/url argument (and url field shows blank, not display the extrrnal link's url address in url input box.
  Support history shows an identical problem in Ff ~117 reported (Aug '23, I think)   (if the condition of Firefox not currently running is same, which I haven't yet been able to determine) and apparently resolved then ( 2 replies, but thread is not visible because FF Support has it recorded as "Archived").
[With ~Ff 123?8 and now 124 installed on iOS 17.3 platform updated a couple weeks ago from iOS 15.+ on my iPhone XR] For couple weeks , following any external link/reference, such as all 'unsubscribe' links from Apple Mail messages, Firefox opens but homepage rather than to the link/url argument (and url field shows blank, not display the extrrnal link's url address in url input box. Support history shows an identical problem in Ff ~117 reported (Aug '23, I think) (if the condition of Firefox not currently running is same, which I haven't yet been able to determine) and apparently resolved then ( 2 replies, but thread is not visible because FF Support has it recorded as "Archived").

Усі відповіді (1)

more options

Hi there, I thank you for this report. It appears that you have discovered a bug that has resurfaced. You can track the progress of the bug here. Staff and contributors are currently working on it, and a fix should be delivered in a release coming later this week (Firefox for iOS 124.1).

I apologise for any inconvenience this may have caused, and thank you for your understanding.