Window Resize Manager

Privacy, support, and release information for Window Resize Manager.

View the Project on GitHub Gevorg-Glechyan/window-size-extension

Chrome Web Store Submission

Use this guide to prepare the public Chrome Web Store listing for Window Resize Manager. Keep it aligned with public/manifest.json, docs/privacy-policy.md, docs/chrome-web-store-privacy.md, docs/chrome-web-store-review.md, docs/usage-analytics-events.md, and the current external release ZIP.

Current Readiness

Already present:

Still missing before final submission:

Single Purpose

Use this single-purpose statement in Chrome Web Store review fields:

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.

Extension Description

Short description:

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

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.
- Refill the custom size form from up to three recent custom dimensions.
- 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, recent custom dimensions, 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. Productivity is also defensible if the listing is positioned for a broader workflow audience, but Developer Tools better matches responsive QA, design, and screenshot workflows.

Screenshot Checklist

Capture screenshots from the production external build loaded from dist/chromium/external. Suggested coverage:

Do not use the internal build for public screenshots.

Chrome Submission Instructions

  1. Confirm the repository state is clean enough for release.

    git status --short
    
  2. Confirm the version in package.json, package-lock.json, and public/manifest.json matches the release being uploaded.

    node -p "require('./package.json').version"
    node -p "require('./package-lock.json').version"
    node -p "require('./public/manifest.json').version"
    
  3. Run the release gate.

    npm run check:release
    

    This runs lint, typecheck, unit tests, privacy validation, external and internal Chromium packaging, and package validation.

  4. Upload the Chromium external ZIP.

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

    Do not upload the -internal.zip package to the public Chrome Web Store.

  5. In the Store listing tab, paste the short and detailed descriptions from this guide.

  6. Add screenshots and promotional images captured from the external build.

  7. Set the public support and privacy URLs after they are published.

    Privacy policy: https://gevorg-glechyan.github.io/window-size-extension/privacy-policy/
    Support: https://gevorg-glechyan.github.io/window-size-extension/support/
    
  8. Complete the privacy questionnaire from docs/chrome-web-store-privacy.md.

    Key answers:

    • remote code: no;
    • Chrome extension permissions: windows, storage, activeTab, scripting;
    • host access: none;
    • data collection: explicit cookieless extension usage analytics only;
    • data use: analytics are used only to improve extension behavior, reliability, and feature adoption.
  9. Use the permission justifications from docs/chrome-web-store-privacy.md and docs/chrome-web-store-review.md.

  10. Before submitting for review, preview the listing and confirm:

    • the privacy policy and support URLs open successfully;
    • the uploaded package is the external Chromium ZIP for the intended version;
    • the dashboard does not show host access prompts;
    • the dashboard permission prompts match the expected manifest permissions;
    • screenshots are legible in the dashboard preview;
    • no internal-only branding appears in public listing copy or screenshots.
  11. Submit for review.

  12. After approval, add the public Chrome Web Store URL to the README, support page, and docs index.