Chrome Now Saves Scroll Position, Filled Forms When Sending Tabs Between Devices

TL;DR

Prime Big Deal Days · Oct 6–7Offer from Amazon

Get the latest gadgets delivered free — and shop member deals

• Fast, free delivery on millions of items
• Access to Prime Big Deal Days deals on October 6–7
• Prime Video, Amazon Music and more included

Start your free Prime trial →Free trial for eligible customers · Cancel anytime

As an affiliate, we earn on qualifying purchases.Hide

Search and coverage interest is spiking around a reported Chrome capability to preserve scroll position and filled form data when sending tabs between devices. The trigger is unconfirmed, and no official Google announcement has been verified. The reports suggest a feature that would carry reading position and in-progress form entries across Chrome’s cross-device tab sharing.

Search and coverage interest is spiking around a reported Chrome capability to preserve scroll position and filled form data when a user sends a tab between devices. The trigger for the surge is unconfirmed, and no official Google announcement has been verified. The reports point to a feature that would carry over a page’s reading position and partially completed form entries during Chrome’s cross-device tab sharing — a change that would meaningfully improve continuity for users who move between desktop and mobile throughout the day.

The underlying topic is well established. Chrome has long offered a ‘send tab to your devices’ option, tied to Chrome Sync, that lets users push an open tab from one device to another. What appears to be new is the reported preservation of two specific states: the scroll position within the page and any text a user has typed into form fields. Both behaviors are familiar in other browser contexts — scroll restoration on back and forward navigation has existed for years, and form data persistence is a common feature — but carrying them across a device transfer is a different technical challenge.

The spike in coverage and search interest suggests the reports are resonating with users, but the source of the signal is not verified. It could stem from a Chrome beta or Canary build change, a developer blog post, a social media thread, or an unconfirmed rumor. As of publication, no official Google statement, Chrome release note, or named engineering source has been confirmed. The reports should therefore be treated as a developing signal rather than a confirmed product change.

Why Scroll and Form Preservation Matters

If the reports are accurate, the change would address a persistent pain point in cross-device browsing. Today, sending a tab typically drops the user at the top of the page, losing both reading position and any in-progress form input. For long articles, research sessions, e-commerce checkouts, and multi-step forms, that interruption can force users to redo work or scroll back through lengthy pages.

The feature would also fit Google’s broader push toward seamless cross-device experiences, where work started on one device continues on another without friction. It would strengthen Chrome’s position against browsers that already offer similar continuity features, and it would give users a practical reason to rely on Chrome’s tab-sharing rather than third-party bookmark or read-it-later services.

Chrome’s Cross-Device Tab Sharing History

Chrome Sync has synced bookmarks, passwords, history, and open tabs across devices for more than a decade. The ‘send tab to your devices’ option, available from the browser menu and right-click context menu, has been a standard part of that ecosystem for years. Scroll restoration on navigation is a long-standing browser behavior, but form state preservation is more complex because it touches on security and privacy — browsers generally avoid persisting sensitive fields such as passwords and payment data without explicit user consent.

Google has been steadily iterating on tab management and cross-device features, including tab groups, tab search, and improved sync behavior. A feature that preserves page state across device transfers would be a logical extension of that work, but it has not been officially documented in Chrome’s public release notes.

Unconfirmed Trigger and Open Questions

The trigger for the current interest is unconfirmed. It is not yet clear whether the reports describe a live feature in a current Chrome build, a change in a beta or Canary channel, a planned update, or a misunderstanding of existing behavior. No official Google announcement, Chromium blog post, or release note has been verified.

Several details remain unknown: which platforms the feature would cover, whether form data is preserved for all field types or only some, and how the feature handles sensitive information such as passwords and payment fields. The security and privacy implications of syncing partially filled forms across devices have not been addressed by any confirmed source.

Watching for Official Chrome Confirmation

Until Google confirms the change, users can monitor Chrome’s release channels — Canary, Beta, and Stable — and the official Chromium blog for updates. The feature, if real, would likely appear first in a developer or beta channel before reaching stable builds. Users who rely on cross-device tab sharing can also test current behavior by sending a tab between their own devices to see whether scroll position and form data persist, though results will vary by platform and Chrome version.

Key Questions

Has Google officially announced this feature?

No. The trigger for the current coverage is unconfirmed, and no official Google announcement, release note, or named source has been verified.

How does sending tabs between devices currently work?

Chrome’s ‘send tab to your devices’ option, tied to Chrome Sync, pushes an open tab from one device to another. It has been a standard feature for years, available from the browser menu and right-click context menu.

Will my form data be synced across devices?

Unclear. The reports suggest filled form data may be preserved, but details on which field types are covered and how sensitive data is handled have not been confirmed.

Which platforms would this affect?

Unknown. No confirmed source has specified whether the feature covers desktop, Android, iOS, or a combination of platforms.

How can I check if I have this feature?

Check Chrome’s release notes and update channels. The feature, if real, would likely appear first in Canary or Beta before reaching Stable builds.

Source: rss