As per comment#0 it seems to a feature request.

Hence, making it as untriaged and asking dev team to kindly look  into it.

Thanks...!!

This would be pretty cool, but might require a significant change to the bookmarks code.  I don't think this is something we'll get to in the immediate future, but if someone wanted to investigate this, we'd be happy to offer guidance!

TBH I don't think this is feasible. Sync has to support merging two bookmarks trees, and at that point we'd have to re-assign IDs  (when two identical bookmarks have different IDs, or when the same ID is used for different bookmarks), basically breaking the current promise.

mamir@: Do you think this is feasible with the new bookmarks Sync design? If not, it's probably fair to close this as WontFix/infeasible.

Introducing stable ids for bookmarks is something that we considered and thoroughly investigated.
The new bookmarks sync design doesn't necessarily make it easier or harder.

I think the issue of merging two bookmark trees isn't the show stopper.
We could at least try to keep this promise across all sync'ing devices. (after the initial sync)

The least intrusive solution that comes to my mind is to store the sync_server_id in the bookmark model itself, such that the bookmark API can provide this id as a stable id for this bookmark across devices.

It's worth noting though that this approach won't benefit sync merge logic, because such id will only be available after the initial sync is finished.

I think if there is a clear use case for that, this could be something we can move forward.

My initial use case is to display a list of user-customized websites(title and link), like many new tab extensions did. 

To implement this, one way is to save a list of user selected bookmarks(an array of bookmark id) in chrome.storage.sync/local . That is ok if only used on the same device. But it is not feasible for cross devices, for example, saving bookmark ids in chrome.storage.sync. Although chrome.storage.sync is cross devices synced, but bookmark id has changed on other devices. 

If don't use build-in bookmarks for websites, use chrome.storage.local to save [[title, link], ... ] directly. It also works locally, but doesn't work cross devices. Because chrome.storage.sync is very limited size(102KB) for storage, it is not suitable for storing lots of titles and links.

So it’s hard to implement this if only use chrome extensions internal mechanisms.

Another possible way is to implement a backend service that can auth user and provide cloud storage. This way bypasses chrome internal restrictions, but need to implement a backend service. Implementing a backend service(or using firebase) is not easy compared with using chrome internal mechanisms. PS: I have implemented this using firebase.

This is why I originally wanted bookmarks id is consistent on different devices.