Chrome Web Store Review Notes

These notes are the source text for Chrome Web Store dashboard review fields. They should be rechecked before every public submission.

See also:

• docs/privacy-policy.md for the public privacy policy.
• docs/support.md for public support, troubleshooting, and install instructions.
• CHANGELOG.md for the canonical release history.
• docs/chrome-web-store-privacy.md for the Developer Dashboard privacy field worksheet.
• docs/chrome-web-store-submission.md for listing copy and submission steps.

Single Purpose

Use this single-purpose statement for Chrome Web Store review:

Window Resize Manager lets users read current Chrome window and viewport dimensions, then resize the current normal Chrome browser window from a toolbar popup using built-in presets, locally saved custom presets, or manually entered dimensions.

Submission Readiness

Already present in the repo:

• Manifest V3 extension metadata and icons.
• Store-facing permission rationale.
• Production build, package ZIP, privacy, and release validation scripts.
• GitHub Pages configured for main:/docs.
• Public-facing privacy policy draft at docs/privacy-policy.md.
• Chrome Web Store privacy worksheet at docs/chrome-web-store-privacy.md.
• Chrome Web Store submission guide at docs/chrome-web-store-submission.md.
• Public support page draft at docs/support.md.
• Usage analytics event inventory at docs/usage-analytics-events.md.
• Canonical changelog at CHANGELOG.md.

Still needed before first Chrome Web Store submission:

• Publish this docs update to main and confirm the privacy/support URLs open before using them in the Chrome Web Store dashboard.
• Capture store screenshots from the production external build.
• Create any required promotional images in the dimensions requested by the Chrome Web Store dashboard.
• Replace any placeholder listing or support URLs after the store listing is approved.

Store Listing Copy

Use this short description for the Chrome Web Store listing:

Resize Chrome windows and check frame or viewport dimensions from a local toolbar popup.

Use this detailed description:

Window Resize Manager helps developers, designers, QA testers, and screenshot workflows resize Chrome browser windows without leaving the toolbar.

Core features:
- Resize the current Chrome window with built-in Phone, Tablet, Laptop, Desktop, and Social/Screenshot presets.
- Enter a custom width and height, then rotate the size when orientation changes.
- Save, edit, delete, and reuse custom presets locally.
- Switch between outer window sizing and visible viewport sizing.
- Read the current window frame size and viewport size from the popup.
- Restore maximized windows to normal size when applying a resize.

Privacy and storage:
- Presets and settings stay in Chrome extension storage on your device.
- Both Chrome build variants send explicit cookieless usage analytics to PostHog EU Cloud with a `build_variant` event property.
- The extension does not request host permissions and does not read page content, selected text, full URLs, cookies, website storage, form data, or browsing history.
- Analytics events do not include page content, tab titles, preset names, exact dimensions, raw error messages, cookies, or stable personal identifiers.
- Viewport mode uses a user-triggered one-shot numeric measurement of the active tab only when Chrome allows it.

Window Resize Manager is built for Chrome Manifest V3 and uses a normal extension toolbar popup.

Recommended category: Developer Tools. If the listing is positioned for a broader non-developer audience, Productivity is also defensible, but Developer Tools better matches responsive QA, design, and screenshot workflows.

Chrome Submission Instructions

1. Run the release validation gate:

   npm run check:release
   

2. Confirm the external package exists and passed validation:

   artifacts/window-resize-manager-chromium-<version>.zip
   

3. Inspect the ZIP contents before upload. The ZIP should contain extension files at the root, including manifest.json, popup.html, background.js, bundled assets, and icons. It should not contain dist/, __MACOSX/, or .DS_Store entries.

4. Load the external production build locally from dist/chromium/external in chrome://extensions and smoke test:

   • Popup rendering and focus behavior.
   • Current frame and viewport size readout.
   • Built-in preset resize.
   • Custom size resize and rotate.
   • Save, edit, delete, and apply local custom presets.
   • Window size mode and viewport size mode.
   • Minimized, maximized, fullscreen, restricted, or unavailable window errors.

5. In the Chrome Web Store dashboard, create or update the item and upload the external ZIP from artifacts/.

6. Fill listing fields:

   • Name: Window Resize Manager
   • Short description: use the short description above.
   • Detailed description: use the detailed description above.
   • Category: Developer Tools
   • Language: choose the listing’s intended default locale.
   • Support URL: use the public support or repository issue URL.
   • Privacy policy URL: use the published URL for docs/privacy-policy.md.

7. Fill privacy practices to match current behavior:

   • Data collection: disclose first-party extension usage analytics for the external build.
   • Host permissions: none.
   • Remote code: none.
   • Data sale or transfer: none.
   • Analytics, telemetry, ads, or tracking: explicit cookieless usage analytics only; no ads, hidden tracking, autocapture, session replay, or surveys.
   • User activity, website content, browsing history, authentication data, financial data, health data, personal communications, and location: not collected.

8. Use the permission rationale below for permission review prompts.

9. Submit for review. After approval, update any public docs that still use a placeholder Chrome Web Store listing URL.

Permission Rationale

The extension requests only these Chrome permissions:

• windows: reads the current Chrome window frame dimensions and state, then resizes the current normal browser window when a user applies a preset or custom size.
• storage: saves user-created window presets, recent custom dimensions, and the selected resize target mode locally in Chrome extension storage.
• activeTab: allows the extension to measure the active tab only after a user invokes the extension for the current-window readout or a viewport resize action.
• scripting: runs a one-shot measurement probe for current viewport readout and viewport size mode when page script measurement is available. The probe reads numeric viewport dimensions only; default pages that block script measurement use Chrome’s active-tab dimensions instead.

No host permissions, optional host permissions, or broad tabs permission are requested in the MVP manifest.

Site Access And Data Collection

The MVP does not request host permissions, optional host permissions, manifest-declared content scripts, DevTools APIs, broad tab access, or website storage access. It does not read page content, selected text, full page URLs, cookies, website localStorage, or form data.

The popup and viewport size mode use activeTab and scripting only for a user-triggered measurement of innerWidth and innerHeight on the active tab. For default pages that block script measurement, the extension falls back to Chrome’s numeric active-tab width and height metadata. The result is used locally to show the current viewport or calculate the required outer Chrome window size. The extension does not store or transmit those measurements.

Both Chrome build variants send explicit cookieless usage analytics to PostHog EU Cloud at https://eu.i.posthog.com. Events are limited to popup opens, resize requests and outcomes, custom preset actions, and resize target setting changes. Properties are enum values, booleans, and low-cardinality buckets, including build_variant values of external or internal. They do not include page content, selected text, full URLs, tab titles, preset names, exact dimensions, raw error messages, cookies, or stable personal identifiers.

The extension does not include account, cloud sync, billing, team workspace, ads, session replay, surveys, or network-backed feature behavior beyond the documented PostHog usage analytics endpoint.

Local Storage Behavior

Custom presets, up to three latest custom dimensions, and the selected resize target mode are stored locally through Chrome extension storage.

Built-in presets are bundled with the extension and are not collected from users.

Store Disclosure Implications

Current Chrome Web Store disclosure answers should reflect:

• No host access.
• No remote code.
• Both build variants connect only to PostHog EU Cloud for first-party usage analytics.
• No sale or transfer of user data.
• No collection of website content, browsing history, URLs, authentication data, financial data, health data, personal communications, or precise location.
• Limited activeTab and scripting use for user-triggered viewport measurement only.

Any future permission increase, network destination, analytics event, content script, host access, or page-data access must be reviewed before implementation and documented here before release.