Opera Extensions API and the Proposed chrome.history.query Cursor Pagination: Compatibility Question

Goal: Allow Opera extensions to retrieve large history or bookmark result sets in manageable chunks without exceeding the 30-second service-worker CPU limit.

Current constraints: chrome.history.search caps maxResults at 100000 and offers no native cursor or token-based pagination; extensions must manually offset or filter by time, which can break if history IDs change across devices. The Manifest V3 service worker terminates after ~30s of CPU work, making single-shot processing of >10k entries unreliable.

Uncertainty: Opera may adopt the proposed chrome.history.query API from the Web Extensions Community Group, which introduces cursor-based pagination, or it may retain Chrome’s offset-only model.

Will Opera implement the chrome.history.query API with cursor support in a future stable release? If adopted, how will the API appear in Manifest V3 service workers? What fallback strategies should extensions use if the API remains unavailable?