Skip to content

[Due for payment 2026-07-21] Add ~100 pixels of scroll offset when deep linking to unread/linked report action #92152

Closed

Description

@melvin-bot

Summary

When opening a report at a linked or unread report action (introduced in #90072), the action currently anchors at the very bottom of the chat. Users see what looks like a single new message, miss earlier unread messages above it, and often don't realize there are more until they send a reply (which then triggers a scroll). The experience reads as broken.

A previous attempt to vertically center the action (#90375, addressing #88502) was closed because computing the action's height accurately added significant initial render delay (see margelo thread).

Proposal

Keep deep linking to the oldest unread (or linked) action as today, but after landing, scroll the chat forward by a fixed offset (~100 px) so a sliver of later content is visible underneath the anchored message. This hints "there is more here" without requiring dynamic per-row height measurement, which is what blocked #90375.

Ideally the offset is applied as part of the initial scroll position rather than a deferred second scroll, to avoid a visible flicker.

Acceptance criteria

  • Opening a report with unread messages still scrolls to the oldest unread action / unread marker.
  • The anchored action no longer renders flush against the bottom of the chat — ~100 px of additional content is visible below it (or, when there are no later messages, the bottom is reached as today).
  • No visible flicker on initial render.
  • Verified on web, desktop, iOS, Android, mWeb.

Context

Slack thread: https://expensify.slack.com/archives/C049HHMV9SM/p1779764974326039

Related:

Issue OwnerCurrent Issue Owner: @JS00001

Activity

  1. aimane-chnaif commented on Jun 2, 2026

    @aimane-chnaif
    Contributor

    @MelvinBot implement this

  2. MelvinBot commented on Jun 2, 2026

    @MelvinBot
    Contributor

    ⏱️ Ran out of time before I could finish. This usually means the task was too complex or I got stuck exploring. Please try again with a more specific request or post in #melvinbot-ai.

    Run details

  3. aimane-chnaif commented on Jun 2, 2026

    @aimane-chnaif
    Contributor

    @MelvinBot implement this

  4. MelvinBot commented on Jun 2, 2026

    @MelvinBot
    Contributor

    ⏱️ Ran out of time before I could finish. This usually means the task was too complex or I got stuck exploring. Please try again with a more specific request or post in #melvinbot-ai.

    Run details

  5. aimane-chnaif commented on Jun 2, 2026

    @aimane-chnaif
    Contributor

    @MelvinBot implement this

  6. MelvinBot commented on Jun 2, 2026

    @MelvinBot
    Contributor

    ⏱️ Ran out of time before I could finish. This usually means the task was too complex or I got stuck exploring. Please try again with a more specific request or post in #melvinbot-ai.

    Run details

  7. aimane-chnaif commented on Jun 3, 2026

    @aimane-chnaif
    Contributor

    @MelvinBot implement this

  8. MelvinBot commented on Jun 3, 2026

    @MelvinBot
    Contributor

    🤖 Draft PR created: #92469
    Please mark it as "Ready for review" when it is ready for review.

  9. VickyStash commented on Jun 12, 2026

    @VickyStash
    Contributor

    Latest info can be found in slack: link

  10. VickyStash commented on Jun 15, 2026

    @VickyStash
    Contributor

    Updates:

    • I've cleaned up the code, removed useFlashListScrollKey hook at all
    • reduced the amount of jumps/flickering during linking
    • clarifying how linking should work on initial data load in slack
  11. mallenexpensify commented on Jun 16, 2026

    @mallenexpensify
    Contributor

    @VickyStash should be be assigned and made owner here
    Also... quick 👀 on the below to see if it's an exact dupe or not? Regardless... since progress is being made here, my guess is it's best to put that one on hold? Thx

  12. VickyStash commented on Jun 16, 2026

    @VickyStash
    Contributor

    Hey @mallenexpensify, yeah, it would be nice to assign me to this one
    Right now it's more about centering the linked message in the viewport.
    Btw, regarding the potential duplicate, I'm not sure it's actualy a dupe, left my comment there

  13. 99 remaining items

  14. aimane-chnaif commented on Aug 8, 2026

    @aimane-chnaif
    Contributor

    For visibility:

  15. JS00001 commented on Aug 10, 2026

    @JS00001
    Contributor

    $375 seems fair to me

  16. mallenexpensify commented on Aug 10, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor+: @aimane-chnaif due $375 via NewDot

  17. added and removed on Aug 11, 2026
  18. garrettmknight commented on Aug 25, 2026

    @garrettmknight
    Contributor

    $375 approved for @aimane-chnaif

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionDailyKSv2ImprovementItem broken or needs improvement.ai

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions