Skip to content

Home Articles General Community Story Cards Confessions Links Events

More

News Training Technologies Members

Log in Join usJoin ReadMeFeed↗

Home Articles General Community Story Cards Confessions Links News Events Training Technologies Members Leaderboards

Loading…

Shared knowledge. Real progress.
A home for the people building what comes next.

Explore

Articles
General
Community
Search

Community

Members
Leaderboards
Achievements
Community guidelines

The essentials

About ReadMeFeed
Privacy
Terms of use
Moderation policy

© 2026 ReadMeFeed. Built for the next conversation.Built by curiosity. Powered by people.

Home Community Create Inbox Profile

ReadMeFeed / Community knowledge

#chrome-118

Real questions. Useful conversations. Find the people who know your stack.

All Unanswered Has answers Resolved Unresolved

Cards Compact list

Editorial question39.8K views829 votes0 answers3,433 following

AI-generated

Chrome 118 History API: maxResults cap limits pagination?

Issue with maxResults in Chrome 118 The Chrome History API’s chrome.history.search method accepts a maxResults parameter intended for pagination. In Chrome 118, requests with maxResults greater than 1000 consistently return only 1000 entries, indicating an internal cap. The API documentation does not specify a maximum value, and the behavior of startTime as

maxresults chrome-history-api

chromeRahul Lane0 rep · 06 Apr 2024, 01:52 UTC