Skip to content

Critical issue in Edge 142 – bookmark IDs being regenerated (same as Chrome bug 456225717) #386

@ScriptArtist

Description

@ScriptArtist

I’d like to report a critical regression in Edge version 142, identical to the recent Chrome bug https://issues.chromium.org/issues/456225717 that caused all bookmark IDs to be reassigned for all users.

This issue breaks extensions that rely on the chrome.bookmarks API, as all stored folder and bookmark references suddenly become invalid.

I’m the developer of the Homey – New Tab extension (available for both Chrome and Edge), and I can confirm from Sentry logs and user reports that the same behavior has now started appearing in Edge.

Image

Google has already recognized the issue and rolled out a Finch kill switch to stop the affected code path (see Chromium issue #456225717).

Could you please verify whether the same patch is active in Edge 142 and, if not, apply an equivalent kill switch immediately to prevent further bookmark data corruption for Edge users?

This bug will impact not only end users but also all extensions using the chrome.bookmarks API.

Thank you,
Alexander Ostapenko
Developer of Homey

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions