# Developer's submission log ties Chrome Web Store review speed to permission changes

A dev.to author publishing as glenkit reports that three permission-neutral updates to two Manifest V3 extensions cleared review within hours to a day, while a listing-text trademark problem drew a rejection in about ten minutes — timings the author calls one person's dataset, not an industry average.

Canonical URL: https://freelancenews.online/news/developer-s-submission-log-ties-chrome-web-store-review-speed-to-230d6dff
Published: 2026-11-08T14:18:15.512Z
Updated: 2026-11-08T14:18:15.512Z
Source published: 2026-11-08T14:01:31.000Z
Event date: Not established
Review status: source-reviewed
Review method: Automated comparison against retrieved source text; not independent fact-checking.

## Report

A developer posting on dev.to under the handle glenkit has published a timestamped account of Chrome Web Store submissions, arguing that review duration tracks whether an extension's permission string changed rather than how much code shipped. The author says they keep timestamps for every submission of their extensions and presents the spread as a pattern they describe as "boring and consistent." The post is a first-person record, and the author states plainly that the timings should be read as one person's dataset rather than an industry average.

The extensions in the log are CookieGuard, which the author says rejects cookie consent banners and requests storage plus a host permission, and AnkiMate, which turns web pages into Anki cards and requests contextMenus, storage, sidePanel, scripting, tabs and a host permission. Both are described as already published, Manifest V3, running no remote code, and — a point the author stresses — never having widened their permission strings since first approval.

Three updates are detailed as permission-neutral. CookieGuard 1.3.0 to 1.4.0 changed the upgrade button so it opened a Creem checkout URL instead of the author's website, and added a yearly-plan link, with no permission changes and a handful of new locale keys. It was submitted on a Friday afternoon and live by the evening, with the public listing showing the new version number a few hours later.

AnkiMate 1.3.0 to 1.4.0 was larger in code: a fallback export path using TSV instead of AnkiConnect, a keyboard command bound to Alt+Shift+D, and three read-only AnkiConnect stats calls. The permission string stayed identical to 1.3.0, and the author reports it went live later that night after an evening submission.

In one pass, CookieGuard moved from 1.4.0 to 1.4.1 with per-site action overrides, a welcome page shown on first run, a reworked diagnostics line in the popup, and a rewritten store description bundled together. Within a day, according to the author, it was approved. Three approvals with no additional review rounds are noted across all three, and the single shared property is identified: the permission string stayed the same.

The counter-case in the post is a submission on a different extension that came back in roughly ten minutes. The author says the cause was not code but a listing description that named competitor products as a comparison — a trademark issue rather than a functionality issue — and that the package was never inspected. The author's reading is that listing text is checked mechanically, so a rejection arriving within minutes should be assumed to concern the description rather than the code.

The author's explanation for why permission changes cost days is that Chrome's review escalates when the permission warning shown to users changes, because a reviewer must then judge whether the new capability is justified by what the description promises. The author calls that a subjective call that moves the submission into a slower queue. This is the author's account of the mechanism; the post cites no Google documentation and no reviewer-side data.

From that model the author derives two rules. Batch permission changes, so that adding host access for one more API domain ships together with every other permission-adjacent change already queued, rather than paying the slow review twice. And do not hesitate to ship genuinely permission-neutral releases, since same-day approval is described as normal rather than lucky.

The post also lists factors that, in the author's experience, seemed not to affect timing: shipping nine locales instead of English-only; listing-text changes bundled with a code update (covered by one review); screenshot and icon changes; and how long the description runs, provided it remains beneath the 16,000-character limit and does not resemble keyword stuffing. By contrast, remotely hosted logic or remote code is described as landing in a queue of its own.

Mismatches between store copy and behavior are the subject of the most consequential warning. When a description makes claims the package does not implement, the author says, the result is not merely slow approval but a rejection cause, and a reviewer can install the extension and check. Before submitting, the author now searches their own codebase for every feature name appearing in a listing. A further warning in the post: editing a listing while a submission is under review can reset its state.

For freelancers and developers who ship browser extensions for clients, the log suggests a scheduling implication rather than a guarantee: permission-adjacent work is the item to plan lead time around, while copy, locale and UI changes can plausibly be bundled into releases that do not touch permissions. That reading is editorial interpretation of one developer's timings, not a measured distribution, and it should not be used to promise a client a delivery date.

What the author recommends is a small submission log: timestamp, whether the permission diff was yes or no, what changed, and approval timestamp. After four or five entries, the author says, this yields a better estimate for a given extension than any blog post, including this one. Two habits the author wishes they had adopted earlier: recording every released version's exact permission string so that "did this change?" becomes a diff rather than a memory exercise, and diffing the store description against the code before each submission.

What the evidence does not establish is substantial. The post's title refers to six submissions, but the excerpts detail three permission-neutral updates plus one rejection on a different extension; the remaining submissions are not described. There is one developer, one account and the author's own recollection of timestamps, and the author notes review behavior varies by category and account history.

No permission-changing submission is timed in the log, so the claim that permission changes cost days rests on contrast with the fast approvals rather than on a measured slow case. The ten-minute rejection is described without the listing text or the rejection notice. No Google policy document, reviewer communication or third-party dataset is cited, and the escalation mechanism is the author's model of the process rather than a confirmed description of Chrome's queueing.

The useful conclusion is procedural. The log is a template for building your own evidence: record permission diffs and timestamps, check listing claims against shipped features, avoid editing a listing mid-review, and group permission changes deliberately. Whether those habits shorten review times is untested here; what the author documents is that, in their own submissions, permission-neutral updates were approved quickly and a listing-text problem was caught almost immediately.

## Key points

- The author reports three permission-neutral updates across CookieGuard and AnkiMate approved within hours to a day, and attributes the speed to unchanged permission strings.
- A submission on a different extension was rejected in about ten minutes over competitor product names in the listing description, which the author says was a trademark issue rather than a code problem.
- The author's stated model is that Chrome escalates review when the user-facing permission warning changes, requiring a subjective justification check; no Google documentation is cited.
- The post recommends batching permission changes, diffing store copy against shipped features, and keeping a personal log of submission and approval timestamps.
- The dataset is one developer's own records, which the author explicitly calls one person's data rather than an industry average.

## Practical implications — editorial interpretation

Editorial interpretation: for client work, treat permission-adjacent extension releases as the items needing schedule buffer, and bundle copy, locale and UI changes into releases that do not touch permissions. Do not promise clients review timelines based on this log — it is one developer's own records, and the author says review behavior varies by category and account history.

## Limitations and unknowns

One developer, one account and the author's own timestamps, not independently verified. The title refers to six submissions, but the excerpts detail only three permission-neutral updates plus one rejection on a different extension. No permission-changing submission is timed, so the 'days' claim rests on contrast rather than a measured slow case. No Google policy documentation, reviewer communication or third-party dataset is cited, and the escalation mechanism is the author's explanation. The ten-minute rejection is described without the listing text or rejection notice.

## Sources

- [1] dev.to: What Chrome Web Store review time actually looks like in 2026 (measured on 6 submissions)
  https://dev.to/glenkit/what-chrome-web-store-review-time-actually-looks-like-in-2026-measured-on-6-submissions-310k
  Retrieved: 2026-11-08T14:17:16.018Z

## Claim references

- The author reports that three permission-neutral updates to two extensions were approved within hours to a day. [source 1]
- The author says a submission on a different extension was rejected in about ten minutes because the listing description named competitor products, a trademark issue, and that the package was not inspected. [source 1]
- The author's explanation is that Chrome escalates review when the permission warning shown to users changes, requiring a subjective justification judgment. [source 1]
- The author advises batching permission changes to avoid paying a slow review more than once. [source 1]
- The author states the timings are one person's dataset rather than an industry average. [source 1]
- The author recommends logging submission timestamps, permission diffs and approval timestamps to estimate review time for one's own extension. [source 1]
