webcompat / web-bugs

A place to report bugs on websites.
https://webcompat.com
Mozilla Public License 2.0
742 stars 65 forks source link

www.facebook.com - desktop site instead of mobile site #131467

Closed esoterica3 closed 9 months ago

esoterica3 commented 9 months ago

URL: https://www.facebook.com/

Browser / Version: Firefox 122.0 Operating System: Windows 10 Tested Another Browser: Yes Other

Problem type: Desktop site instead of mobile site Description: Desktop site instead of mobile site Steps to Reproduce: Faceback feed is not working since the last update. It just keeps loading, then shows an error that something is wrong. Feed Is fine on mobile ff, regular FF, tor, chrome, and all else. Does not help to disable add blocks.

View the screenshot Screenshot
Browser Configuration
  • gfx.webrender.software: false
  • blockList: basic
  • hasTouchScreen: false
  • frameworks: {'fastclick': False, 'mobify': False, 'marfeel': False}
  • mixed active content blocked: false
  • mixed passive content blocked: false
  • tracking content blocked: false

View console log messages

From webcompat.com with ❤️

sv-calin commented 9 months ago

We appreciate your report but I was not able to reproduce this issue.

image

Tested on: • Browser / Version: Firefox Beta 122 • Operating System: Windows 10

Suggestions: • Clear cache/data/cookies, disable Ad-blocker (if available), or use a clean profile and check again • If there are any changes made to the default settings of the browser (e.g. in about:config), please revert to the default settings

How to create a new profile:

  1. Open a new tab
  2. Type in the address bar "about:profiles"
  3. Press "Enter"
  4. Click on "Create a New Profile"
  5. Click "Next"
  6. Name your profile
  7. Click "Finish"
  8. Head to your newly created profile
  9. Click "Launch profile in new browser"

Note: You can return to your old profile at any given time by accessing "about:profiles" in the address bar

[qa_52/2023]

sv-calin commented 9 months ago

Closing this as worksforme since we were not able to reproduce this issue. Feel free to reopen if the issue still occurs after following the suggestions and leave a comment with more details.

[inv_02/2024]