Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Can’t open Facebook marketplace posts on Firefox mobile.

  • 2 replies
  • 1 has this problem
  • 1 view
  • Last reply by 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.

All Replies (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