Closed Bug 1866266 Opened 5 months ago Closed 5 months ago

Enable LargestContentfulPaint in Release


(Core :: Performance, task)




122 Branch
Tracking Status
relnote-firefox --- 122+
firefox122 --- fixed


(Reporter: sefeng, Assigned: sefeng)



(Keywords: dev-doc-complete)


(1 file)

No description provided.
Assignee: nobody → sefeng

Release Note Request (optional, but appreciated)
[Why is this notable]: This is one of the most wanted Web Performance API
[Affects Firefox for Android]: Yes
[Suggested wording]: The LargestContentfulPaint API has now been added, to provide timing information about the largest or text paint before users interact a web page.
[Links (documentation, blog post, etc)]:

relnote-firefox: --- → ?
Pushed by
Enable LargestContentfulPaint in Release r=emilio
Closed: 5 months ago
Resolution: --- → FIXED
Target Milestone: --- → 122 Branch

Added a slightly reworded note to the Fx122 nightly release notes, please allow 30 mins for the site to update.
Keeping the relnote-firefox flag as ? to keep it on the radar for inclusion in the final Fx122 release notes

Comment on attachment 9365198 [details]
Bug 1866266 - Enable LargestContentfulPaint in Release r=emilio

Beta/Release Uplift Approval Request

  • User impact if declined: One of the most wanted web performance API will be shipped one version late
  • Is this code covered by automated tests?: Yes
  • Has the fix been verified in Nightly?: Yes
  • Needs manual test from QE?: No
  • If yes, steps to reproduce:
  • List of other uplifts needed: Bug 1867266
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): The feature itself has been running on Nightly for a while so it's working as expected. This change is about turning that on in Release which is low risky.
  • String changes made/needed:
  • Is Android affected?: Yes
Attachment #9365198 - Flags: approval-mozilla-beta?

I'm not super crazy about enabling this so late in the cycle when it's been off for the first half of the Beta cycle (i.e. NIGHTLY_BUILD vs. EARLY_BETA_OR_EARLIER). How concerned are we about that?

Flags: needinfo?(sefeng)

oh I didn't aware this is too late now as I thought we still have like 2 weeks. But yeah, if it's being considered as late in the cycle, please approval-mozilla-beta- . I'd also love to make sure it's stable for a long enough time.

Flags: needinfo?(sefeng)

Comment on attachment 9365198 [details]
Bug 1866266 - Enable LargestContentfulPaint in Release r=emilio

If this had ridden 121 to Beta behind an EARLY_BETA_OR_EARLIER flag (or even if that had been landed earlier in the cycle), I think it would have been reasonable to request this now when you did. But having been completely disabled on Beta for the last 2 weeks leaves me feeling less confident about that. If there isn't a strong business need for this to ship this cycle, I'd vote for letting it ride 122 instead. Don't hesitate to reach out if we need to discuss further!

Attachment #9365198 - Flags: approval-mozilla-beta? → approval-mozilla-beta-

MDN updates for this can be tracked in the following GitHub issue:

You need to log in before you can comment on or make changes to this bug.