Closed Bug 1897067 Opened 4 months ago Closed 2 days ago

facebook.com - Missing timestamps for posts in ESR version

Categories

(Web Compatibility :: Site Reports, defect, P2)

Desktop
Windows 10

Tracking

(firefox-esr115 wontfix, firefox126 unaffected, firefox128 unaffected)

RESOLVED WONTFIX
Tracking Status
firefox-esr115 --- wontfix
firefox126 --- unaffected
firefox128 --- unaffected

People

(Reporter: rbucata, Unassigned)

References

()

Details

(Keywords: webcompat:contact-ready, webcompat:needs-diagnosis)

User Story

platform:windows,mac,linux
impact:feature-broken
configuration:common
affects:all

Attachments

(1 file)

Environment:
Operating system: Windows 10
Firefox version: ESR 115.11

Preconditions:
Account previously created

Steps to reproduce:

  1. Navigate to: https://www.facebook.com/?locale=ro_RO
  2. Perform account login
  3. Scroll the feed and observe the posts

Expected Behavior:
Timestamps are present

Actual Behavior:
Timestamps are missing

Notes:

  • Reproduces regardless of the status of ETP
  • Does not reproduce in Firefox Nightly, Firefox Release, Chrome

Created from https://github.com/webcompat/web-bugs/issues/136988

Attached video 20240516_064544.mp4
OS: Unspecified → Windows 10
Hardware: Unspecified → Desktop

Does anyone have any insight on this? I know quite a number of people this issue is affecting, and it seems to only be people with the ESR build of Firefox. Any help and a potential fix would be greatly appreciated.

Tom, do you mind checking if we can find the fix-revision here?

Severity: -- → S4
User Story: (updated)
Flags: needinfo?(twisniewski)
Priority: -- → P2

Any update on a potential fix for this issue? It's been going on for 3 weeks now. Was hoping there would be some sort of resolution by now.

You can get a resolution right now by using a newer version of Firefox.

Even if we identify the patch that fixes this, it's highly questionable if we're able to uplift that into the 115 ESR (especially since we'll be releasing an 128 ESR in July) - and even if we do uplift it into ESR115, it will take quite some time for that to be included in an update for ESR115. Moving slow is kinda the whole point of ESR.

(In reply to Dennis Schubert [:denschub] from comment #5)

You can get a resolution right now by using a newer version of Firefox.

Even if we identify the patch that fixes this, it's highly questionable if we're able to uplift that into the 115 ESR (especially since we'll be releasing an 128 ESR in July) - and even if we do uplift it into ESR115, it will take quite some time for that to be included in an update for ESR115. Moving slow is kinda the whole point of ESR.

I'm using Windows 8.1 currently. So unless there is a newer version of Firefox compatible with 8.1 that I'm not aware of, that's why I'm using ESR.

The timestamps missing in Facebook is something I've started getting used to. It's an annoyance, but it's not the end of the world. Guess I better keep getting used to it, or just use Chrome when I want to go on Facebook.

Guess I just assumed this would be a relatively easy fix, since it seems to involve a missing code, or changing code, or whatever is causing the timestamps to be missing in Firefox ESR. But I know next to nothing about this sort of thing, and you guys are the experts.

Appreciate your response, appreciate the work you guys do.

Duplicate of this bug: 1902272

(In reply to DanNJ316 from comment #2)

Does anyone have any insight on this? I know quite a number of people this issue is affecting, and it seems to only be people with the ESR build of Firefox. Any help and a potential fix would be greatly appreciated.

Somebody in another forum provided this fix and it works!: Set dom.textMetrics.fontBoundingBox.enabled to true in about:config.

(In reply to mn2482 from comment #8)

(In reply to DanNJ316 from comment #2)

Does anyone have any insight on this? I know quite a number of people this issue is affecting, and it seems to only be people with the ESR build of Firefox. Any help and a potential fix would be greatly appreciated.

Somebody in another forum provided this fix and it works!: Set dom.textMetrics.fontBoundingBox.enabled to true in about:config.

I tried it and it does indeed work! It took some time, but I figured somebody would come up with a fix at some point.

Thank you very much!

Setting the mentioned config to true also fixed it for a FB group member who is using v82 on Linux.

Depends on: 1801198
Flags: needinfo?(twisniewski)

The fixing patch likely won't get uplifted to 115 as uplifts only limited to security patches.

Status: NEW → RESOLVED
Closed: 2 days ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: