Mozilla VPN is currently experiencing an outage. Our team is actively working to resolve the issue. Please check the status page for real-time updates. Thank you for your patience.

Om de ûnderfining foar jo te ferbetterjen is tydlik de funksjonaliteit dan dizze website troch ûnderhâldswurk beheind. Wannear in artikel jo probleem net oplost en jo in fraach stelle wolle, kin ús stipemienskip jo helpe yn @FirefoxSupport op Twitter en /r/firefox op Reddit.

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Can’t open Facebook marketplace posts on Firefox mobile.

  • 2 antwurd
  • 1 hat dit probleem
  • 1 werjefte
  • Lêste antwurd fan Eve

more options

When browsing Facebook marketplace on Firefox mobile I click on a post that I want more details on. This should open a new tab with the post and images. Instead Firefox opens a new blank tab but does not continue onto the actual post. The address bar reads - about:blank. This was working a week or so ago.

I checked this behavior in safari and marketplace works as intended. I can click an ad and it correctly opens a new tab with more info/photos.

I’m on iPhone 6s, using iOS 13.3.1

Any help troubleshooting this would be appreciated.

When browsing Facebook marketplace on Firefox mobile I click on a post that I want more details on. This should open a new tab with the post and images. Instead Firefox opens a new blank tab but does not continue onto the actual post. The address bar reads - about:blank. This was working a week or so ago. I checked this behavior in safari and marketplace works as intended. I can click an ad and it correctly opens a new tab with more info/photos. I’m on iPhone 6s, using iOS 13.3.1 Any help troubleshooting this would be appreciated.

Alle antwurden (2)

more options

I'm seeing this too. I'm looking into if it's already been reported elsewhere. If it hasn't, I'll file a bug for it.

more options

I reported this as a bug for iOS FF devs